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/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/harden)<a href="https://agentmods.dev/commands/varunk130/ai-workflow-playbooks/harden"><img src="https://agentmods.dev/badge/commands/varunk130/ai-workflow-playbooks/harden/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/varunk130/ai-workflow-playbooks/harden"><img src="https://agentmods.dev/badge/commands/varunk130/ai-workflow-playbooks/harden.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.00000 | $0.00116 |
| Opus 5 | $0.00000 | $0.00058 |
| Sonnet 5 | $0.00000 | $0.00023 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
harden 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.
What it actually says
Run the HARDEN stage of the AI Workflow Playbooks pipeline.
Load and execute:
playbooks/threat-mitigation/PLAYBOOK.md- Systematic security review across all boundariesplaybooks/throughput-tuning/PLAYBOOK.md- Measure-first performance optimization
Also load supporting runbooks as needed:
runbooks/security-baseline.md- Detailed security checklistrunbooks/performance-baseline.md- Performance targets and measurement tools
Produce a security audit report and a performance assessment with specific findings and recommendations.
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 · 12 lines · 0 tokens per session scan A a2c6d4ede965
harden 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 116 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
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.
repurpose
Workflow recipe — turn one blog post, video, or idea into a full platform-native content pack (thread, LinkedIn, newsletter, carousel, short-form script) with sharp hooks and a thumbnail concept.
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.
land-a-job
Workflow recipe — go after a specific role end to end by chaining 4 skills: decode the JD, research the company, tailor your application, and prep the interview.
ship-a-feature
Workflow recipe — take a feature idea from fuzzy brief to launch plan by chaining 5 skills.