Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Larens94/codednaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/larens94/codedna/init)<a href="https://agentmods.dev/commands/larens94/codedna/init"><img src="https://agentmods.dev/badge/commands/larens94/codedna/init/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/larens94/codedna/init"><img src="https://agentmods.dev/badge/commands/larens94/codedna/init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00028 | $0.02604 |
| Opus 5.5 | $0.00011 | $0.01042 |
| Sonnet 5.5 | $0.00006 | $0.00521 |
| Haiku 4.5 | $0.00003 | $0.00260 |
Grade A, and why
init scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/codedna:init $ARGUMENTS
Annotate every unannotated source file in the project with a CodeDNA module header.
If $ARGUMENTS is provided, treat it as the target path. Otherwise use the current working directory.
Step 0 — Silent scan + present choices
0a — Auto-detect (silent, no output yet)
- Scan the target directory for all source files. Skip:
vendor/,node_modules/,venv/,.venv/,__pycache__/,.git/,dist/,build/,migrations/. - Detect extensions present:
.py,.php,.blade.php,.ts,.tsx,.js,.mjs,.go,.rs,.java,.kt,.rb,.cs,.vue,.svelte - Count total files to annotate (exclude already-annotated files).
- Check if CodeDNA CLI is installed:
python3 -c "import codedna_tool; print('ok')" 2>/dev/null
0b — Present first choice: execution mode
Print this box and wait for the user's answer:
┌─────────────────────────────────────────────────┐
│ CodeDNA Init — <path> │
│ Languages detected: .php, .blade.php, .ts, .tsx │
│ Files to annotate: 230 │
│ │
│ How should I annotate? │
│ │
│ [A] Use this Claude session │
│ Deep rules: via LLM, uses session tokens │
│ ~<estimate based on file count> │
│ │
│ [B] Use codedna CLI (tree-sitter + AST) ✓ │
│ Fast structural pass, zero LLM cost │
│ Requires: pipx install git+https://github.com/Larens94/codedna.git │
│ │
└─────────────────────────────────────────────────┘
Choice [A/B]:
If CLI is not installed, mark option B with (not installed) instead of ✓ and note it requires Python 3.11+.
If user picks B but CLI is not installed: Do NOT silently fall back to A. Instead print:
CodeDNA CLI is required for option B. Install it with:
pipx install git+https://github.com/Larens94/codedna.git
Requires Python 3.11+. After installing, run /codedna:init again.
Stop here — do not proceed.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 297 lines · 28 tokens per session scan A fd7f8b430282
init is a command published in the GitHub repository Larens94/codedna (151 stars, last pushed 9d ago), licensed MIT. It adds 28 tokens to every session and 2,604 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
add-endpoint
Scaffold a new API endpoint with full layering.
AGENTS
Per-command agent-optimized usage and structure guide.
pn-audit-security
OWASP-guided security review — auth posture, input validation, secrets, CORS, JWT, rate limiting. Surgical command for backend security. Use standalone or as part of pn-backend-audit.
catalog-integrations
Wraps agents/integration-catalog-builder/AGENT.md. Named Credentials + Remote Sites + Connected Apps + Auth Providers + Certificates, cross-referenced with Apex/Flow usage, scored for posture.
/opsx-apply
Implement tasks from an OpenSpec change (Experimental).
api-endpoints
Create comprehensive FastAPI endpoints with proper structure, validation, and documentation.