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 skills/marconae/speq-skill/speq-clinpx skills add marconae/speq-skill --skill speq-cligit clone --depth 1 https://github.com/marconae/speq-skillWhat 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.00421 |
| Opus 5 | $0.00024 | $0.00211 |
| Sonnet 5 | $0.00010 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
speq-cli 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.
What it actually says
speq CLI
Spec-driven development via the speq CLI. The spec CLI is installed locally and available in the path. Invoke via speq.
Search-First Rule
Never read full spec files without searching first.
Apply information foraging — search narrows the scent trail before committing context window budget.
Command Reference
| Command | Purpose |
|---|---|
speq domain list |
List all domains |
speq feature list |
Tree view of all features |
speq feature list <domain> |
Features in a domain |
speq feature get <domain>/<feature> |
Full feature spec |
speq feature get "<domain>/<feature>/<scenario>" |
Single scenario |
speq search query "<query>" |
Semantic search |
speq feature validate |
Validate all specs |
speq feature validate <domain>/<feature> |
Validate single feature |
Workflow
1. Search first
speq search query "<relevant terms>"
2. Get specific content
speq feature get "<domain>/<feature>/<scenario>"
3. Validate after changes
speq feature validate
Example
Finding error handling scenarios:
# Search for related scenarios
speq search query "error handling validation"
# Get specific scenario
speq feature get "cli/validate/Validation fails on missing field"
# Validate structure
speq feature validate cli/validate
Anti-Pattern
# Wrong: Loading entire spec files
cat specs/cli/validate/spec.md
# Right: Search and get specific
speq search query "validation"
speq feature get "cli/validate/Required field missing"
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 · 67 lines · 48 tokens per session scan A d5a8affb19a9
speq-cli is a skill published in the GitHub repository marconae/speq-skill (50 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 421 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 skills, from other repositories
build-executor
Govern implementation from an approved execution contract. Invoke when execution-contract.md is approved and the user wants disciplined build work, TDD execution, or guarded batch-by-batch implementation.
workflow-start
Primary entry point for the spec-superflow state-machine workflow. Invoke when the user is inside an active spec-superflow change directory (look for .spec-superflow.yaml, changes/ /, proposal.md, specs/, design.md, tasks.md, or execution-contract.md) and asks to start, continue, resume, implement, plan, or figure out…
release-archivist
Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.
bug-investigator
Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.
spec-writer
Create or refine spec-superflow planning artifacts. Invoke when the change is understood well enough to write proposal.md, specs/, design.md, and tasks.md.
contract-builder
Convert approved planning artifacts into an execution contract. Invoke when the user wants to start building, asks to move from planning to implementation, or when execution-contract.md is missing or stale.