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 commands/varunk130/ai-workflow-playbooks/validategit clone --depth 1 https://github.com/varunk130/ai-workflow-playbooksWrote 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/varunk130/ai-workflow-playbooks/validate)<a href="https://agentmods.dev/commands/varunk130/ai-workflow-playbooks/validate"><img src="https://agentmods.dev/badge/commands/varunk130/ai-workflow-playbooks/validate.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 | $0.00000 | $0.00151 |
| Opus 5 | $0.00000 | $0.00076 |
| Sonnet 5 | $0.00000 | $0.00030 |
| Haiku 4.5 | $0.00000 | $0.00015 |
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 4d 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
Run the VALIDATE stage of the AI Workflow Playbooks pipeline.
Load and execute:
playbooks/peer-review-protocol/PLAYBOOK.md- Multi-axis code review with severity classification
Review the code across five axes: correctness, readability, architecture fitness, security surface, and performance impact. Produce a structured review with a verdict (APPROVE or REQUEST_CHANGES) and categorized findings.
Optionally load guardians for specialist perspective:
guardians/architecture-guardian.md- For system design reviewguardians/quality-guardian.md- For test coverage assessmentguardians/security-guardian.md- For security auditguardians/operations-guardian.md- For operational readiness
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.
- 4d ago First seen · 13 lines · 0 tokens per session scan A 17681d715373
validate is a command published in the GitHub repository varunk130/ai-workflow-playbooks (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 151 tokens. 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 commands, from other repositories
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.
design-review
Workflow recipe — review a design end-to-end, ending in measured numbers rather than adjectives, by chaining 4 skills.
firm
Convene your standing AI staff — memos on every beat, a board session without you, minutes with dissent preserved.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
ship-a-feature
Workflow recipe — take a feature idea from fuzzy brief to launch plan by chaining 5 skills.