Leave the evidence. Bury the secrets.
Security logging prompts for AI coding agents.
Add security logging to an existing application in small, verified waves.
Inspired by Trim Reaper and Grim Prompter.
- Open your application in a coding agent.
- Paste the shared instruction, then the assessment prompt. Identify the service to review.
- Run the foundation prompt, then one bounded wave at a time. Verify each change and keep the resulting ledger for your next session.
For file-based use, give the agent this checkout's path and the selected prompt. Resolve library references here and make changes in the application checkout. For clipboard use, include the security event checklist with the shared instruction and assessment prompt. Assessment reviews all 90 items, then adds requirements specific to the application.
| Pass | Purpose | Prompt |
|---|---|---|
| Assess | Inventory code, controls, consumers, and evidence gaps | 01 · Assess |
| Wave 0 · Foundation | Safe schema, existing logger integration, privacy, bounded delivery | 02 · Foundation |
| Wave 1 · Critical gaps | Privileged actions, sensitive operations, monitoring tampering | 03 · Critical |
| Wave 2 · High gaps | Authentication, authorization, recovery, and sessions | 04 · High |
| Wave 3 · Medium gaps | Validation, abuse controls, uploads, and workflow failures | 05 · Medium |
| Wave 4 · Lower-priority context | Useful lifecycle and investigation context | 06 · Context |
| Every wave | Adversarial tests, consumer checks, canary and rollback plan | 07 · Verify and roll out |
| Focused repair | Existing logs leak data, inject records, or exhaust resources | 08 · Repair |
| Ongoing | Review a diff for lost coverage or schema drift | 09 · Change review |
Wave priority reflects the consequences of a coverage gap, not the event's logger level. Reorder waves for your application's risks; establish the safe foundation first. Keep deployment separate from local implementation and report checks not run.
- Runbook: scope, gates, and a reusable private ledger.
- Security event checklist: 90 review items spanning identity, data, infrastructure, delivery, AI agents, and audit health.
- Coverage: application-specific inventory and evidence requirements.
- Event contract: privacy, trusted fields, compatibility, and delivery semantics.
- Verification: application-specific safety checks.
Created by Jim Manico of manicode.ai and Manicode Security.
For teams looking to guide secure coding from the start, manicode.ai offers commercial secure-coding prompts for AI assistants, designed to reduce avoidable security rework and the time and tokens spent on it.
Dread Ledger's original prompts and documentation are licensed under the MIT License. Copyright (c) 2026 Jim Manico.