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/impact)<a href="https://agentmods.dev/commands/larens94/codedna/impact"><img src="https://agentmods.dev/badge/commands/larens94/codedna/impact/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/impact"><img src="https://agentmods.dev/badge/commands/larens94/codedna/impact.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.00018 | $0.00368 |
| Opus 5.5 | $0.00007 | $0.00147 |
| Sonnet 5.5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
impact 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:impact $ARGUMENTS
Perform a cascade impact analysis for the file at path $ARGUMENTS.
If no argument is provided, ask: "Which file do you want to analyze? Provide the path relative to the project root."
Steps:
-
Read the target file's module docstring (first 15 lines only). Extract its
exports:andused_by:fields. -
For each file listed in
used_by:, read only its module docstring and extract its ownused_by:(to find second-level callers). -
Build the cascade chain — stop at 3 levels deep to avoid infinite loops.
-
Output the impact tree:
Impact Analysis: utils/format.py
=================================
Direct callers (Level 1):
- api/routes.py
exports: revenue_route(req) -> Response
rules: all routes require auth middleware
- views/dashboard.py
exports: render(ctx) -> str
rules: none
Second-level callers (Level 2):
- workers/report.py (calls api/routes.py)
exports: generate(period) -> None
Cascade summary:
Editing utils/format.py may affect 3 files.
Check rules: in api/routes.py before changing format_currency signature.
- If the file has no
used_by:entries or is not annotated, output:
utils/new_file.py has no used_by: entries — no cascade impact detected.
Note: file may not be annotated yet. Run /codedna:check to verify.
Use this command before any refactor, signature change, or deletion.
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 · 48 lines · 18 tokens per session scan A 8793c2c2fa58
impact is a command published in the GitHub repository Larens94/codedna (151 stars, last pushed 9d ago), licensed MIT. It adds 18 tokens to every session and 368 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
mempalace-init
Set up MemPalace — install the package, initialize a palace, register the MCP server with Cursor, and verify everything works.
help
Show comprehensive MemPalace help — available skills, MCP tools, CLI commands, hooks, and architecture.
search
Search your memories across the MemPalace using semantic search with wing/room filtering.
mempalace-status
Show the current state of your memory palace — wings, rooms, drawer counts, and suggestions.
test-cards
Display Stripe test card numbers for various testing scenarios.
AGENTS
Per-command agent-optimized usage and structure guide.