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 wedabro/bro-skills --skill speckit.validategit clone --depth 1 https://github.com/wedabro/bro-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/skills/wedabro/bro-skills/speckit.validate)<a href="https://agentmods.dev/skills/wedabro/bro-skills/speckit.validate"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.validate/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/wedabro/bro-skills/speckit.validate"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.validate.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.00014 | $0.00591 |
| Opus 5 | $0.00007 | $0.00296 |
| Sonnet 5 | $0.00003 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
speckit.validate 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 Mission
Check whether the ENTIRE implementation meets spec.md or not — final gate before deploying.
📥 Input
- All artifacts: spec.md, plan.md, tasks.md
- Source code (implementation)
.agents/memory/constitution.md.agents/project.json, dependency manifests, and documented verification commands
📋 Protocol
- Tasks Completion: All tasks in tasks.md have
[X]? - Success Criteria: All SCs in spec.md passed?
- Capability Discovery:
- Detect project type, language, package manager, containerization, configured services, build/test commands, and health checks.
- Produce an applicability table. A non-applicable check is
N/A, not PASS.
- Build Verification (MUST run applicable commands):
- Run the repository-defined build/type/lint commands.
- Use the matching container service when the constitution requires Docker.
- For non-Docker projects, use the documented project runtime.
- Any applicable build failure → ❌ BLOCKED.
- Runtime Verification (when the project has a runtime):
- Start the documented runtime or discovered Compose configuration.
- Wait using health/retry behavior with a bounded timeout; do not use a fixed sleep as proof of readiness.
- Inspect failing service/application logs immediately.
- Health Check (when configured):
- Read health endpoints and ports from project configuration or environment.
- Verify the expected status/body. Do not assume web/admin/API services.
- Tests and Success Criteria:
- Run the configured test suite and verify each spec success criterion with evidence. Missing required evidence → ❌ BLOCKED.
- Constitution Check: No rules violated?
- Final Verdict:
🏁 VALIDATION REPORT ═══════════════════════ Tasks: 15/15 ✅ Build: PASS ✅ Runtime: N/A (library project) Health: N/A (no network service) Tests: PASS ✅ Constitution: PASS ✅ ─────────────────────── VERDICT: ✅ READY FOR DEPLOY
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 · 63 lines · 14 tokens per session scan A 8ae6089387bc
speckit.validate is a skill published in the GitHub repository wedabro/bro-skills (2 stars, last pushed 13d ago), licensed MIT. It adds 14 tokens to every session and 591 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-31.
Other skills, from other repositories
junior-to-senior
Adversarial senior-engineer review for agent-generated plans, designs, and architectures. Treats the current output as junior work, constructs a senior reviewer whose domain expertise comes from live codebase research plus web research of current best practices, diagnoses altitude failures (too vague or too granular)…
resolve-pr-comments
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments. Handles both change requests (fix or skip) and reviewer questions (explain using reasoning recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comments", "fix review comments", "address PR…
map-codebase
Deep architecture report that fans out parallel inspections across different aspects of the codebase (structure, tech stack, APIs, patterns, data flow, dependencies, testing) and synthesizes findings into a comprehensive document at .turbo/codebase-map.md and .turbo/codebase-map.html. Use when the user asks to "map…
reply-to-pr-threads
Draft, confirm, and post replies to GitHub PR review threads. Handles per-category reply formatting, re-fetches thread resolution state so auto-resolved threads are skipped, and posts via GraphQL. Use when the user asks to "reply to PR threads", "post PR thread replies", or "draft PR reply messages".
answer-reviewer-questions
For each reviewer question on a PR, recall implementation reasoning and compose a raw answer. Use when the user asks to "answer reviewer questions", "draft answers to PR questions", or "explain reviewer questions".
codex-review
Run AI-powered code review using the codex CLI. Use when the user asks to "codex review", "run codex review", or "review a commit with codex".