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/verifygit 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.00026 | $0.00235 |
| Opus 5 | $0.00013 | $0.00118 |
| Sonnet 5 | $0.00005 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
verify 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.
What it actually says
Refresh the last_verified_at timestamp on a node. Use this after you
have manually re-inspected the referenced code and confirmed the node
still describes it correctly.
Steps
-
Run:
dt verify $ARGUMENTS -
Report the result in one line. If the command succeeds, say: "Verified — last_verified_at=." If it fails (node not found), say so and suggest
dt_queryor/dt:showto find the correct id.
When to use
- After a manual inspection of the code a node describes.
- In response to a
reconcilefinding understaleornever_verified. - Not as a way to "silence" reconcile without actually looking at the code. The verification flag carries meaning; don't spam it.
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.
- 2d ago First seen · 31 lines · 0 tokens per session scan A 72a308d16fce
verify is a command published in the GitHub repository yacb2/domaintome (0 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 235 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
resume
Auto-detect and resume any interrupted Plan Cascade task. Detects mega-plan, hybrid-worktree, or hybrid-auto context and routes to the appropriate resume command.
spec-plan
Run a resumable spec interview to produce spec.json/spec.md (planning-time), then optionally compile to prd.json. Usage: /plan-cascade:spec-plan " " [--output-dir ] [--flow ] [--first-principles] [--max-questions N] [--feature-slug ] [--compile] [--tdd ] [--confirm] [--no-confirm].
gsd:eval-review
Audit an executed AI phase's evaluation coverage and produce an EVAL-REVIEW.md remediation plan.
discovery-ping
Discovery-plugin self-test. Exercises the plugin-shipped slash command path so we can capture commandsource/expansiontype values via the hook dumps.
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.