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.
git clone --depth 1 https://github.com/dceoy/speckit-agent-skillsWrote 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/agents/dceoy/speckit-agent-skills/speckit.clarify)<a href="https://agentmods.dev/agents/dceoy/speckit-agent-skills/speckit.clarify"><img src="https://agentmods.dev/badge/agents/dceoy/speckit-agent-skills/speckit.clarify.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.1 | $0.00027 | $0.04069 |
| Opus 5 | $0.00014 | $0.02034 |
| Sonnet 5 | $0.00005 | $0.00814 |
| Haiku 4.5 | $0.00003 | $0.00407 |
Grade A, and why
speckit.clarify 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 8d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 8d ago First seen · 303 lines · 27 tokens per session scan A 21b4508ce24d
speckit.clarify is an agent published in the GitHub repository dceoy/speckit-agent-skills (130 stars, last pushed 12d ago), licensed AGPL-3.0. It adds 27 tokens to every session and 4,069 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-30.
Other agents, from other repositories
library-advisor
Use when choosing libraries, evaluating npm packages, deciding build vs buy, researching technology choices, or comparing library options.
empathy-reviewer
Use when reviewing UX, user experience, interfaces, user-facing features, or need empathy/design perspective on code changes.
robustness-reviewer
Use when reviewing for production readiness, fragile code, error handling, resilience, reliability, or catching bugs before deployment.
architecture-auditor
Use when reviewing architecture, checking design patterns, auditing dependencies, or catching structural problems before they multiply.
autonomous-developer
Use when completing tasks autonomously, working independently, delivering PR-ready code, or needing end-to-end implementation without supervision.
code-consistency-reviewer
Use when scanning for code pattern inconsistencies - prop naming, implementation approaches, boolean conventions, import patterns, deprecated usage.