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/showgit 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/show)<a href="https://agentmods.dev/commands/yacb2/domaintome/show"><img src="https://agentmods.dev/badge/commands/yacb2/domaintome/show.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.00021 | $0.00412 |
| Opus 5 | $0.00010 | $0.00206 |
| Sonnet 5 | $0.00004 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
show 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.
What it actually says
Call dt_get_node(id="$ARGUMENTS", include_edges=True) and render the
node as a readable Markdown briefing. Treat each node as a "reference
page" — DomainTome is meant to be the central entry point to everything known
about a concept.
Render shape
# <title> [<type> · <status>]
<body — render as Markdown verbatim, do not summarize>
## Links
<if metadata.links is a non-empty array, render each as a bullet:
`- [<title>](<url>) _<type if set>_`. If empty, skip this section.>
## References
<if metadata.source_ref is set, render as inline code.
if metadata.source is set, render as `Source: <source> (confidence: <confidence>)`.
if metadata.last_verified_at is set, render as `Last verified: <date>`.
if metadata.deprecated_at is set, render with reason.>
## Relations
### Outgoing
<grouped by relation: e.g. `- implements → capability-foo`>
### Incoming
<grouped by relation: e.g. `- flow-bar --implements-->`>
## Raw metadata
<remaining keys from metadata that weren't already rendered above,
compact JSON.>
Rules
- Do not summarize or paraphrase
body. Print it verbatim as Markdown. - If a metadata key was rendered in "Links" / "References" sections, do not repeat it in "Raw metadata".
- If a key is not set, skip the section entirely — no "N/A" or "none".
- If the node is not found, suggest
dt_query("$ARGUMENTS")to search by title or id fragment.
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 · 50 lines · 21 tokens per session scan A e475448f8068
show is a command published in the GitHub repository yacb2/domaintome (0 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 412 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-31.
Other commands, from other repositories
ingest
Lite ingest — fetch a paper and write a short 4-section triage summary (Key Takeaways, Background, Main Idea & Summary, Critique). No figures, fast.
pith
Control Pith token compression modes and access structured output formats, wiki, and status.
budget
Set a hard token ceiling per response (e.g. /budget 100) or clear it (/budget off).
focus
Load only the sections of a file relevant to the current question, reducing context noise.
init
Scaffold a new PaperLoom at the configured path (or at an optional path argument). Idempotent — fills missing files without clobbering existing ones.
mega-approve
Approve the mega-plan and start feature execution. Creates worktrees and generates PRDs for each feature. Usage: /plan-cascade:mega-approve [--flow ] [--tdd ] [--confirm] [--no-confirm] [--spec ] [--first-principles] [--max-questions N] [--auto-prd] [--agent ] [--prd-agent ] [--impl-agent ].