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/check)<a href="https://agentmods.dev/commands/larens94/codedna/check"><img src="https://agentmods.dev/badge/commands/larens94/codedna/check/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/check"><img src="https://agentmods.dev/badge/commands/larens94/codedna/check.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.00015 | $0.00397 |
| Opus 5.5 | $0.00006 | $0.00159 |
| Sonnet 5.5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
check 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.
What it actually says
/codedna:check
Perform a CodeDNA compliance check on the current project. Do the following:
-
Find all source files in the project (
.py,.php,.blade.php,.ts,.tsx,.js,.go,.java,.kt,.rb,.rs,.cs) — excludevendor/,node_modules/,venv/,.venv/,.git/,__pycache__/,dist/,build/,migrations/. -
Check each file for a CodeDNA module annotation:
- Python: first token must be a string literal (module docstring) containing
exports:,used_by:, andrules:fields. - Other languages: first comment block must contain
exports:,used_by:,rules:fields.
- Python: first token must be a string literal (module docstring) containing
-
Check for stale
used_by:references: for everyused_by:entry in every annotated file, verify the referenced file exists. Flag any references to files that no longer exist. -
Check for missing
agent:field in annotated Python files. -
Output a report in this format:
CodeDNA Coverage Report
=======================
Total files: <N>
Annotated: <N> (<pct>%)
Unannotated: <N>
Stale used_by refs: <N>
Unannotated files:
- path/to/file.py
- path/to/file.ts
Stale used_by references:
- utils/format.py → used_by references deleted_file.py (file not found)
If all files are annotated and no stale references exist, output:
CodeDNA: all <N> files annotated, no stale references. Coverage: 100%
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 · 41 lines · 15 tokens per session scan A ce4e67d47133
check is a command published in the GitHub repository Larens94/codedna (151 stars, last pushed 9d ago), licensed MIT. It adds 15 tokens to every session and 397 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
test-cards
Display Stripe test card numbers for various testing scenarios.
AGENTS
Per-command agent-optimized usage and structure guide.
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
fire-verify-uat
Conversational User Acceptance Testing with automatic parallel diagnosis on failures.
fire-test
Run Dominion Flow plugin integration tests to verify all commands and integrations work correctly.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.