A command that imports GitHub Spec Kit artifacts into local Dotdog knowledge graphs. Spec Kit is a format for organizing feature specifications, while a knowledge graph stores connected project information for later use.

Use it in a Spec Kit project containing .specify and specs directories. It imports feature data, optionally replaces generated files when explicitly forced, compiles the graphs, and reports the result.

It turns project specifications into locally compiled graphs without changing the original specification files. Strict input and path checks help keep the import limited to the current project.

import — Command by specdog

Install

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.

agentmods

npx agentmods add commands/specdog/dotdog/import

Clone the repo

git clone --depth 1 https://github.com/specdog/dotdog

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 376 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00010	$0.00376
Opus 5	$0.00005	$0.00188
Sonnet 5	$0.00002	$0.00075
Haiku 4.5	$0.00001	$0.00038

Measured yesterday against content hash 0889cbba160f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

commands/import.md · 48 lines

What it actually says

Import Spec Kit artifacts

Prerequisites

Run this command from the root of a GitHub Spec Kit project containing .specify/ and specs/.
Confirm dotdog --version is 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/ and specs/ directories. Stop on any mismatch.
Run the local-only import:
```
dotdog speckit import . --json
```
Add --force only when $ARGUMENTS is exactly force and 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/ or specs/.
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.

Changes

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 · 48 lines · 10 tokens per session scan A 0889cbba160f

Subscribe to this mod's changes

import is a command published in the GitHub repository specdog/dotdog (4 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 376 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.

Planning ai cli dogfood dotdog spec specification

import

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Import Spec Kit artifacts

Prerequisites

User Input

Steps

Safety

What this file has done since we first saw it

Other commands, from other repositories

checklist

specify

implement

constitution

tasks

speckit.assess.decide