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 skills add synaptiai/synapti-marketplace --skill specification-capturegit clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/skills/synaptiai/synapti-marketplace/specification-capture)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/specification-capture"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/specification-capture/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/skills/synaptiai/synapti-marketplace/specification-capture"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/specification-capture.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.00121 | $0.02652 |
| Opus 5 | $0.00060 | $0.01326 |
| Sonnet 5 | $0.00024 | $0.00530 |
| Haiku 4.5 | $0.00012 | $0.00265 |
Grade A, and why
specification-capture 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 6d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specification Capture
You capture three specification elements that complement an issue's acceptance criteria, and you persist them to the decision journal so every downstream phase (PLAN, CODE, VERIFY) and every related command (/flow:design, /flow:brainstorm) can read from the same source of truth.
This skill owns the capture lifecycle and the journal contract — every consumer (/flow:start, /flow:design, /flow:brainstorm) invokes the skill instead of re-implementing it. Two failure modes the skill prevents:
- No persistence-side check — without a single owner, a command can claim "captured all three" while writing only a partial set to the journal, and the gap silently flows into PLAN.
- No shared source of truth —
commands/design.mdandcommands/brainstorm.mdwould otherwise address overlapping elements (non-goals especially) without reading from or writing to the same.decisions/artifact, so a user running/flow:designfirst and/flow:startsecond would get duplicate or contradictory specifications.
Iron Law
EVERY ISSUE GETS THE THREE ELEMENTS BEFORE PLAN. Acceptance criteria scope WHAT the user-visible outcome is. The three elements scope what the implementation IS NOT, how it behaves under failure, and what schemas it must honor. PLAN cannot fence the implementation without all three.
A captured specification is the contract between the issue and the per-task atomic units the implementation-planner agent produces. Without it, tasks lack failure-mode coverage and interface contracts — the Stranger Test (end-of-PLAN gate in commands/start.md) will fail.
Inputs
The invoking command MUST pass these in the prompt:
- Issue context — title, body, labels, comments. The skill parses these for any specification language already in the issue.
- Journal path — typically
.decisions/issue-{N}.md(where{N}is the issue number). The skill reads this path first to detect prior captures. - Invocation reason — one of
start,design,brainstorm. Used to scope which elements the skill focuses on (see "Per-invoker scope" below).
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.
- 6d ago First seen · 162 lines · 121 tokens per session scan A 04471f1a396e
specification-capture is a skill published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 121 tokens to every session and 2,652 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
create-or-update-concepts
Scan and analyze the project codebase to create or update concept files in agents-context/concepts/ (organized by domains/, source/, shared/) and update the README index and Load-When Cheatsheet.
step2-scope-tasks
Break a specification into ordered task groups with explicit context-awareness directives.
step1-write-spec
Gather requirements through structured Q&A, then formalize into a specification document.
create-pr
Creates a GitHub Pull Request on the current branch with a description focused on WHAT changed (not HOW). Uses emojis in the title and description. Use when the user asks to create a PR, open a pull request, or submit changes for review. Triggers on mentions of PR, pull request, merge request, or code review.
step4-archive-spec
Archive a completed spec — moves it to specs-archived and blocks agent access.
plan-product
Define product mission, vision, target users, and technology stack.