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/fistasolutions/fista-spec-kit/extractgit clone --depth 1 https://github.com/fistasolutions/fista-spec-kitWrote 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/fistasolutions/fista-spec-kit/extract)<a href="https://agentmods.dev/commands/fistasolutions/fista-spec-kit/extract"><img src="https://agentmods.dev/badge/commands/fistasolutions/fista-spec-kit/extract.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.00016 | $0.00900 |
| Opus 5 | $0.00008 | $0.00450 |
| Sonnet 5 | $0.00003 | $0.00180 |
| Haiku 4.5 | $0.00002 | $0.00090 |
Grade A, and why
extract scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://localhost:8000/openapi.json > apps/api/openapi.json How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
If provided, treat $ARGUMENTS as a path (e.g., ./src, ./apps/web, ./apps/api); otherwise default to ./src.
Goal
Convert an existing codebase into structured SpecKit artifacts by automatically scanning its components, routes, and APIs.
This creates a reusable baseline specification that can be extended through /specify, analyzed via /analyze, and executed with /implement.
Use this command when onboarding legacy projects, merging external repos, or preparing for feature expansion.
Inputs
- path (string, default: ./src) — Root folder to analyze.
- openapi (optional string) — Path to OpenAPI JSON if not in common locations.
Steps
-
Resolve Path
- Verify the provided
$ARGUMENTSpath exists. - Normalize slashes for cross-platform support.
- Verify the provided
-
Discover Web Routes
- Glob:
app/**/{page,route}.{ts,tsx,js,jsx} - Extract friendly URLs:
- Strip
/app/prefix and filename. - Normalize
/indexto/. - Keep dynamic
[id]segments.
- Strip
- Glob:
-
Detect UI Components
- Search under
components/,ui/, andshared/directories. - Identify component names from filenames.
- Search under
-
Collect API Endpoints
- Try loading OpenAPI JSON from:
apps/api/openapi.jsonpublic/openapi.json<path>/openapi.json
- Parse endpoint
method,path, andsummary.
- Try loading OpenAPI JSON from:
-
Generate Artifacts (Non-Destructive)
- Create or update:
packages/specs/active/extracted/spec.yamlpackages/specs/active/extracted/inventory.mdpackages/specs/active/extracted/tasks.md
- Append rather than overwrite.
- Include a timestamp for traceability.
- Create or update:
-
Summarize Findings
- Count total routes, components, and API endpoints.
- Display summary in output:
✅ Extracted 18 routes, 7 components, 5 API endpoints. 📝 Wrote: packages/specs/active/extracted/spec.yaml 📝 Wrote: packages/specs/active/extracted/inventory.md 📝 Updated: packages/specs/active/extracted/tasks.md
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.
- 4d ago First seen · 122 lines · 16 tokens per session scan A 8980e40577bc
extract is a command published in the GitHub repository fistasolutions/fista-spec-kit (2 stars, last pushed 10mo ago), licensed MIT. It adds 16 tokens to every session and 900 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.