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/ai-sdlc-framework/ai-sdlc/import-specgit clone --depth 1 https://github.com/ai-sdlc-framework/ai-sdlcWrote 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/ai-sdlc-framework/ai-sdlc/import-spec)<a href="https://agentmods.dev/commands/ai-sdlc-framework/ai-sdlc/import-spec"><img src="https://agentmods.dev/badge/commands/ai-sdlc-framework/ai-sdlc/import-spec.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.00048 | $0.00758 |
| Opus 5 | $0.00024 | $0.00379 |
| Sonnet 5 | $0.00010 | $0.00152 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
import-spec 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Import a spec-kit feature into the AI-SDLC backlog. The spec-kit tasks.md
at --from <path> is parsed; one backlog task is created per upstream task
entry, each carrying a specRef: frontmatter block pointing back to the
upstream artifact.
Per RFC-0036 OQ-1 + OQ-11 (resolved 2026-05-16)
tasks.mdonly. No fallback tospec.md. Missingtasks.md→Decision: incomplete-spec-detectedis opened in the Decision Catalog and a clarification task is filed back in the backlog asking the operator to run/speckit.tasksupstream and re-run the import.- Auto-detect schema; refuse unknown. Unrecognised
tasks.mdlayout →Decision: upstream-schema-unknownis opened + an upgrade-framework task is filed asking for parser support.
Phase scope (Phase 4 of RFC-0036)
- ✓ CLI + slash command
- ✓
specRef:back-references on every generated task - ✗ DoR at import time (Phase 5 / AISDLC-330)
- ✗ Reconcile / drift handling (Phase 6 / AISDLC-331)
Usage
node pipeline-cli/bin/cli-import-spec.mjs --from .specify/specs/<feature>/
$ARGUMENTS is the path. Accepts either the feature directory
(containing tasks.md) or the tasks.md file directly.
ARGS="${ARGUMENTS:-}"
if [[ -z "$ARGS" ]]; then
echo "Usage: /ai-sdlc import-spec --from <path-to-spec-kit-feature>"
exit 1
fi
# Pass the operator's args straight through. `--from` is the only required
# flag; `--work-dir` defaults to cwd; `--format` defaults to text.
node pipeline-cli/bin/cli-import-spec.mjs $ARGS
Output
- Imported: one line per task written, formatted as
IMP-N (upstream T-NNN) → <path>. - Incomplete spec: the Decision id (DEC-NNNN) + path of the clarification task created in
backlog/tasks/. - Unknown schema: same, but the clarification task asks for parser support rather than an upstream re-run.
In all three cases the CLI exits 0 — the failure modes are explicitly non-blocking per RFC-0035 G0. The operator's next triage pass sees the Decision + clarification task and decides next steps.
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 · 69 lines · 48 tokens per session scan A b3753b0bd1b5
import-spec is a command published in the GitHub repository ai-sdlc-framework/ai-sdlc (92 stars, last pushed 10d ago), licensed Apache-2.0. It adds 48 tokens to every session and 758 once invoked, about $0.0002 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-30.
Other commands, from other repositories
spec-intake
Execute the canonical workflow: .agent/workflows/spec-intake.md.
test
Execute the canonical workflow: .agent/workflows/test.md.
research
Research a technical or product question.
session-stop
Stop recording and save this agent session to the project ledger.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
ox-session-pause
belongs in the ox CLI JSON output (guidance field), not here. Skills are agent-specific wrappers; ox serves all agents (Codex, etc.). --> Suspend the current session recording. Local cache continues to receive entries, but the upload at stop time will exclude the suspended range.