agentmods.dev

check

A coverage report for CodeDNA annotations across a project’s source files. It also checks whether documented file references still point to files that exist.

In plain words
What is it for?
Use it to count annotated and unannotated files, find stale `used_by` references, and check required fields in Python annotations.
Why use it?
It shows which files lack the required documentation and identifies references that became outdated after files moved or were removed.

Command

145 5d ago A scan 15 tokens original MIT
View the source file Larens94/codedna
Install

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.

agentmods
npx agentmods add commands/larens94/codedna/check
Clone the repo
git clone --depth 1 https://github.com/Larens94/codedna
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 397 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.00397
Opus 5 $0.00008 $0.00198
Sonnet 5 $0.00003 $0.00079
Haiku 4.5 $0.00002 $0.00040

Measured 2d ago against content hash ce4e67d47133, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

codedna-plugin/commands/check.md · 41 lines

What it actually says

/codedna:check

Perform a CodeDNA compliance check on the current project. Do the following:

  1. Find all source files in the project (.py, .php, .blade.php, .ts, .tsx, .js, .go, .java, .kt, .rb, .rs, .cs) — exclude vendor/, node_modules/, venv/, .venv/, .git/, __pycache__/, dist/, build/, migrations/.

  2. Check each file for a CodeDNA module annotation:

    • Python: first token must be a string literal (module docstring) containing exports:, used_by:, and rules: fields.
    • Other languages: first comment block must contain exports:, used_by:, rules: fields.

  3. Check for stale used_by: references: for every used_by: entry in every annotated file, verify the referenced file exists. Flag any references to files that no longer exist.

  4. Check for missing agent: field in annotated Python files.

  5. 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%
Changes

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.

  1. 2d ago First seen · 41 lines · 15 tokens per session scan A ce4e67d47133

Subscribe to this mod's changes

check is a command published in the GitHub repository Larens94/codedna (145 stars, last pushed 5d ago), licensed MIT. It adds 15 tokens to every session and 397 once invoked, about $0.0001 per session on Opus 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.

Data and AILLMLanguagesTestingaiai-agentscode-annotationdeveloper-toolspython
Related

Other commands, from other repositories

pr-address

Address PR review comments on current branch.

dagster-io/dagster · 7 tokens

statusbar-style

Switch the status-bar style (classic / capsule / hairline).

leeguooooo/claude-code-usage-bar · 13 tokens

init

Command "init" from ErisPulse/ErisPulse, covering erispulse.cli.commands.init 模块, 模块概述, 函数列表, validateprojectname(name: str) and 类列表.

ErisPulse/ErisPulse · 0 tokens

install

Command "install" from ErisPulse/ErisPulse, covering erispulse.cli.commands.install 模块, 模块概述, 类列表 and class installcommand(command).

ErisPulse/ErisPulse · 0 tokens

run

Command "run" from ErisPulse/ErisPulse, covering erispulse.cli.commands.run 模块, 模块概述, 类列表, class reloadhandler(filesystemeventhandler) and class runcommand(command).

ErisPulse/ErisPulse · 0 tokens

language

Command "language" from ErisPulse/ErisPulse, covering erispulse.cli.commands.language 模块, 模块概述, 类列表 and class languagecommand(command).

ErisPulse/ErisPulse · 0 tokens