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/initgit clone --depth 1 https://github.com/yacb2/domaintomeWhat 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.00029 | $0.00291 |
| Opus 5 | $0.00015 | $0.00146 |
| Sonnet 5 | $0.00006 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
init 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 yesterday.
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
/dt:init is a permanent alias for /dt:sync when no graph
exists yet. It is not deprecated — external docs, READMEs, and muscle
memory rely on it, so it stays as a stable first-time-setup entry
point.
Behavior
Run /dt:sync and follow its INIT mode branch end to end. The
detection in §Step 0 of sync.md will land in INIT automatically
when .dt/graph.db does not exist or dt_list(type="module") returns
zero modules.
If you discover the graph already has modules (someone ran setup elsewhere), do not re-seed silently. Stop and tell the user:
"DomainTome already has N top-level modules for this project. Run
/dt:syncwithout arguments to extend (EXTEND mode), or/dt:auditto see current state."
For the full INIT workflow — layout detection, granularity prompt,
manual vs auto-scan, sub-agent template, mandatory dt_audit()
verification — see commands/sync.md §INIT mode.
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.
- yesterday First seen · 28 lines · 29 tokens per session scan A 661e4412f88f
init is a command published in the GitHub repository yacb2/domaintome (0 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 291 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
memory-search
Search agent memory + learned patterns for cross-session context relevant to $ARGUMENTS.
discovery-ping
Discovery-plugin self-test. Exercises the plugin-shipped slash command path so we can capture commandsource/expansiontype values via the hook dumps.
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.
gsd:docs-update
Generate or update project documentation verified against the codebase.