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/juanmhidalgo/claude-pluginsWrote 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/juanmhidalgo/claude-plugins/validate)<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/validate"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/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/commands/juanmhidalgo/claude-plugins/validate"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/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.00030 | $0.00460 |
| Opus 5 | $0.00015 | $0.00230 |
| Sonnet 5 | $0.00006 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
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 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.
What it actually says
PRD to Validate
$ARGUMENTS
Instructions
Use the Agent tool to invoke the prd-validator agent to check if the implementation fulfills the PRD.
The agent should:
-
Load the PRD from file path or GitHub issue URL
-
Extract checkable items:
- Acceptance Criteria
- QA Checklist items
- User Stories (verify flows exist)
-
Explore the codebase to verify each item:
- Search for relevant code implementing each criterion
- Check UI/UX flows if applicable
- Look for tests covering the scenarios
-
Generate validation report:
# PRD Validation: [Feature Name]
## Summary
- ✅ Completed: X/Y criteria
- ⚠️ Partial: X/Y criteria
- ❌ Missing: X/Y criteria
## Acceptance Criteria
### ✅ Completed
- [Criterion] → Found in `path/to/file.py:123`
### ⚠️ Partial
- [Criterion] → Implemented but [what's missing]
### ❌ Missing
- [Criterion] → No implementation found
## Recommendations
- [What to implement next]
- [Potential gaps to address]
- Offer next steps:
- Create GitHub issues for missing items
- Update PRD if scope changed
- Mark items as done in original PRD
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 · 79 lines · 30 tokens per session scan A b26a738a5992
validate is a command published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 460 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-09-03.
Other commands, from other repositories
implement
Execute tasks from a track's implementation plan following TDD workflow.
shipwright-enhance
Add features to an existing Shipwright project.
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
aqa-flow
Router workflow for test automation: routes to ui-aqa-flow, api-aqa-flow, or testgen-flow. Kept for backward compatibility.
sddp-implement-qc-loop
Command description: Run implement and QC in a continuous loop. Argument hint: [optional: feature directory or branch name] Command category: orchestration Prerequisites: spec, plan, tasks.