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 skills/bugroger/beastmode/validatenpx skills add BugRoger/beastmode --skill validategit clone --depth 1 https://github.com/BugRoger/beastmodeWhat 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.00023 | $0.01123 |
| Opus 5 | $0.00012 | $0.00562 |
| Sonnet 5 | $0.00005 | $0.00225 |
| Haiku 4.5 | $0.00002 | $0.00112 |
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 yesterday.
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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/validate
Verify code changes meet quality standards before release.
Guiding Principles
- All features must complete implementation before validation begins
- Fix failures before reporting — attempt repairs, don't just stop at first error
- Gates are pass/fail — no partial credit, no "close enough"
- Validate the artifact, not the process — results matter, not how we got there
Phase 0: Pre-Execute
1. Check Feature Completion
Scan for implementation artifacts to verify all features have been implemented:
ls .beastmode/artifacts/implement/*-$epic-*.md 2>/dev/null
Cross-reference against the feature plan files to determine completion status.
Print status:
Feature Completion Check
────────────────────────
✓ feature-1 — completed
✓ feature-2 — completed
✗ feature-3 — pending
Result: BLOCKED — 1 feature still pending
If any features are NOT completed:
- Print which features are pending
- STOP — do not proceed to test execution
- Suggest: "Run
/beastmode:implement <epic-name>-<pending-feature>to complete remaining features."
If all completed: proceed to next step.
2. Identify Test Strategy
From context, determine:
- Test command (e.g.,
npm test,pytest) - Lint command (if configured)
- Type check command (if configured)
- Custom gates from design acceptance criteria
Phase 1: Execute
1. Run Tests
<test-command>
Capture output and exit code.
2. Run Lint (if configured)
<lint-command>
3. Run Type Check (if configured)
<type-check-command>
4. Run Custom Gates
Execute any custom gates defined in .beastmode/context/VALIDATE.md.
Phase 2: Validate
1. Analyze Results
Check each gate:
- Tests: PASS/FAIL
- Lint: PASS/FAIL/SKIP
- Types: PASS/FAIL/SKIP
- Custom: PASS/FAIL/SKIP
2. Determine Overall Status
- All required gates pass → PASS
- Any required gate fails → FAIL
2b. Identify Failing Features
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.
- yesterday First seen · 214 lines · 23 tokens per session scan A 1c942db7e62b
validate is a skill published in the GitHub repository BugRoger/beastmode (16 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 1,123 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…