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.
npx agentmods add commands/yacb2/domaintome/auditgit clone --depth 1 https://github.com/yacb2/domaintomeWrote 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/yacb2/domaintome/audit)<a href="https://agentmods.dev/commands/yacb2/domaintome/audit"><img src="https://agentmods.dev/badge/commands/yacb2/domaintome/audit.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.00929 |
| Opus 5 | $0.00021 | $0.00464 |
| Sonnet 5 | $0.00008 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
audit 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 3d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dt:audit runs structural checks on a DomainTome graph and surfaces
findings. The target is chosen by $ARGUMENTS:
$ARGUMENTS |
Target | Mechanism |
|---|---|---|
| empty | Active project (the graph the MCP server is using) | MCP dt_audit() |
<path> |
Another project's graph at <path>/.dt/graph.db |
Subprocess dt audit + dt stats |
/dt:probe <path> is a deprecated alias that always lands in the
"with path" branch.
Mode A — active project (no args)
Call dt_audit() via MCP and summarize:
- orphans: nodes with no edges. List them and suggest either linking or deleting each.
- invalid_ids / generic_ids: flag id hygiene problems and propose renames.
- cycles_supersedes / cycles_depends_on / cycles_triggers: any non-empty list is a real bug — explain what it breaks and suggest which edge to remove.
If everything is clean, just say so in one line.
Mode B — external project (path provided)
The MCP server is bound to the active project's graph; it cannot be
re-aimed at a different DB mid-session. So this mode shells out to the
dt CLI instead.
-
Resolve the DB path:
<path>/.dt/graph.db. If the path does not exist, stop and report it clearly — do not create anything. Relative paths resolve against the current working directory. -
Run two read-only CLI calls:
dt audit --db <path>/.dt/graph.db --json dt stats --db <path>/.dt/graph.dbThe
--jsonflag onauditgives you structured counts and findings in one shot:nodes_total,edges_total,nodes_by_type,nodes_by_status,edges_by_relation,last_mutation_at, plus the finding lists (orphans,dangling_edges,invalid_ids,generic_ids,unknown_types,cycles_*). -
Summarize as a single markdown block with this shape:
## DomainTome audit — <project-name> **Graph** - nodes: <nodes_total> edges: <edges_total> - last mutation: <last_mutation_at> - by type: <nodes_by_type as k=v, ...> - by status: <nodes_by_status as k=v, ...> - by relation: <edges_by_relation as k=v, ...> **Health** - orphans: N - dangling_edges: N - invalid_ids / generic_ids / unknown_types: N / N / N - cycles: supersedes=N, depends_on=N, triggers=N **Usage (MCP)** - calls: N errors: N - total bytes exchanged: X (≈ X*0.3 tokens, honest proxy) - top tools: <tool> (N calls), ...
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.
- 3d ago First seen · 95 lines · 42 tokens per session scan A 45b71febaf9f
audit is a command published in the GitHub repository yacb2/domaintome (0 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 929 once invoked, about $0.0002 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-31.
Other commands, from other repositories
mega-plan
Generate a mega-plan for project-level multi-feature orchestration. Breaks a complex project into parallel features with dependencies. Usage: /plan-cascade:mega-plan [--flow ] [--tdd ] [--confirm] [--no-confirm] [--spec ] [--first-principles] [--max-questions N] [design-doc-path].
formula-f10
../../../core/thinkingos/agents/observer.md.
kg-setup
Configure Knowledge Graph path and create config file.
approve
Approve the current PRD and begin parallel story execution. Analyzes dependencies, creates execution batches, launches background Task agents for each story, and monitors progress. Usage: /plan-cascade:approve [--flow ] [--tdd ] [--confirm] [--no-confirm] [--agent ] [--impl-agent ] [--retry-agent ] [--no-verify]…
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
test
Run the full test suite with coverage and report results.