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.
git clone --depth 1 https://github.com/specdog/dotdogWrote 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/specdog/dotdog/import)<a href="https://agentmods.dev/commands/specdog/dotdog/import"><img src="https://agentmods.dev/badge/commands/specdog/dotdog/import/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/specdog/dotdog/import"><img src="https://agentmods.dev/badge/commands/specdog/dotdog/import.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00010 | $0.00376 |
| Opus 5.5 | $0.00004 | $0.00150 |
| Sonnet 5.5 | $0.00002 | $0.00075 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
import 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 1mo 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
Import Spec Kit artifacts
Prerequisites
- Run this command from the root of a GitHub Spec Kit project containing
.specify/andspecs/. - Confirm
dotdog --versionis 0.9.0 or newer.
User Input
$ARGUMENTS
This command accepts either no input or the exact word force. Do not interpolate $ARGUMENTS into a shell command. Reject paths, flags, command substitutions, separators, redirects, and any other input. Work only in the current project root.
Steps
-
Verify that the current directory contains real, non-symlinked
.specify/andspecs/directories. Stop on any mismatch. -
Run the local-only import:
dotdog speckit import . --json -
Add
--forceonly when$ARGUMENTSis exactlyforceand the user explicitly requested replacement of edited generated files:dotdog speckit import . --json --force -
Compile the imported projects:
dotdog compile .doghouse/speckit -
Report the imported feature IDs, written/unchanged/skipped counts, and compile result.
Safety
- Never execute user input as shell text.
- Do not modify
.specify/orspecs/. - Keep generated output under
.doghouse/speckit/. - Do not add network calls, credentials, telemetry, background processes, or elevated privileges.
- Stop and report the error if Dotdog rejects a symlink, protected path, edited output, or out-of-root path.
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.
- 1mo ago First seen · 48 lines · 10 tokens per session scan A 0889cbba160f
import is a command published in the GitHub repository specdog/dotdog (7 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 376 once invoked, about $0.0000 per session on Opus 5.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
okf
Bundle de connaissance OKF dans okf/ : source de vérité (architecture, vision, marketing, roadmap, conventions). Cette commande aiguille vers le bon usage selon $ARGUMENTS.
tree-ring-recall
Recall durable Tree Ring Memory context before starting or resuming work.
tree-ring-update
Check for or install a verified Tree Ring Memory CLI update without changing installation scope.
tree-ring-certify
Generate Tree Ring harness or recall-quality evidence without confusing it with the full framework release suite.
tree-ring-status
Check receipt-backed Tree Ring harness readiness without claiming configuration is activation.
drift-detect
Configuration drift detection command. Finds inconsistencies, orphaned components, and stale content in the Badi system.