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/specdog/dotdog/inspectgit clone --depth 1 https://github.com/specdog/dotdogWhat 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.00007 | $0.00359 |
| Opus 5 | $0.00003 | $0.00179 |
| Sonnet 5 | $0.00001 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
inspect 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
Inspect imported Spec Kit graphs
Prerequisites
- Run this command from the root of the intended Spec Kit project.
- Confirm
dotdog --versionis 0.9.0 or newer. - Confirm
.doghouse/speckit/exists. Run/speckit.dotdog.importfirst when it does not.
User Input
$ARGUMENTS
This command accepts no input. Do not interpolate $ARGUMENTS into a shell command. Stop when any argument is supplied.
Steps
-
Verify
.doghouse/speckit/is a real directory inside the current project root and is not a symlink. -
Compile all imported feature projects:
dotdog compile .doghouse/speckit -
Run structural analysis:
dotdog analyze .doghouse/speckit dotdog design .doghouse/speckit --json -
Enumerate generated
.dagfiles only beneath.doghouse/speckit/. For each regular, non-symlinked file, run:dotdog audit --require-kind entity --json "<verified-dag-file>" -
Report failed audits, missing node kinds, model gaps, and the feature directory for each finding.
Safety
- Never execute user input as shell text.
- Do not follow symlinks or inspect files outside
.doghouse/speckit/. - Do not invent domain requirements or modify source Spec Kit artifacts.
- Do not make network calls, expose listeners, use credentials, or elevate privileges.
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 · 49 lines · 7 tokens per session scan A cecbb83e965d
inspect is a command published in the GitHub repository specdog/dotdog (4 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 359 once invoked, about $0.0000 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
checklist
Generate a custom checklist for the current feature based on user requirements.
specify
Create or update the feature specification from a natural language feature description.
constitution
Create or update the project constitution from interactive or provided principle inputs.
speckit.assess.decide
Apply a go / needs-clarification / kill gate and hand survivors off into Spec-Driven Development.
speckit.assess.research
Gather evidence — users, market, prior art, and data — to support or challenge the idea.
plan
Execute the implementation planning workflow using the plan template to generate design artifacts.