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/impactgit 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/impact)<a href="https://agentmods.dev/commands/yacb2/domaintome/impact"><img src="https://agentmods.dev/badge/commands/yacb2/domaintome/impact.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.00013 | $0.00183 |
| Opus 5 | $0.00006 | $0.00092 |
| Sonnet 5 | $0.00003 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
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 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
Answer "what breaks if I touch $ARGUMENTS?" by:
dt_traverse(from_id="$ARGUMENTS", relations=["depends_on", "triggers", "implements"], max_depth=3)to walk downstream consumers.dt_get_node(id="$ARGUMENTS", include_edges=True)to list incomingenforces,validates,referencesedges.
Summarize as two groups:
- Downstream (things that break): from step 1.
- Upstream (things that protect/reference it): from step 2's incoming.
Flag any node whose status is deprecated/superseded — those are stale.
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 · 21 lines · 13 tokens per session scan A 9a9b10816ea2
impact is a command published in the GitHub repository yacb2/domaintome (0 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 183 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
maestro-next
Unified entry for all development intents — classify intent, assess complexity, route to the correct execution channel: /maestro-companion (lightweight), standard single run, or /maestro and /maestro-ralph (multi-step manual/orchestrated). Pure router, never runs execution loops itself.
axstream-teach
Compile a UI task into a fast replayable macro (do it once, instant forever).
maestro-knowhow
Intent-driven knowhow precipitation — describe what you want to capture (记一个关于X的决策 / 保存这段代码模板 / 写个部署配方 / 存个调试技巧) and the workflow infers the type and records it into .workflow/knowhow/. Pure capture surface; knowhow 的管理/审计走 /maestro-knowledge；项目约束规则走 /maestro-spec add。Triggers on "knowhow capture", "知识沉淀", "沉淀经验"…
auto
AI auto strategy executor. Analyzes task and automatically selects and executes the best strategy: direct execution, hybrid-auto PRD generation, hybrid-worktree isolated development, or mega-plan multi-feature orchestration.
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]…