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/ankushdixit/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/ankushdixit/claude-plugins/validate)<a href="https://agentmods.dev/commands/ankushdixit/claude-plugins/validate"><img src="https://agentmods.dev/badge/commands/ankushdixit/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/ankushdixit/claude-plugins/validate"><img src="https://agentmods.dev/badge/commands/ankushdixit/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.00009 | $0.00194 |
| Opus 5.5 | $0.00004 | $0.00078 |
| Sonnet 5.5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00019 |
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 1mo 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
Session Validate
Run the validation script to check quality standards:
sk validate
To automatically fix linting and formatting issues:
sk validate --fix
The validation checks:
- Tests: All test suites pass
- Linting: Code passes linting rules (auto-fixable with --fix)
- Formatting: Code is properly formatted (auto-fixable with --fix)
- Code Coverage: Meets minimum coverage threshold
- Git Status: Working directory is clean or has expected changes
- Acceptance Criteria: Work item requirements are met
Display the validation results to the user with a clear pass/fail status for each check. If linting or formatting fail, suggest using /validate --fix to automatically fix the issues. This command allows checking quality during development without ending the session.
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.
- 1mo ago First seen · 29 lines · 9 tokens per session scan A 3fd27de3979a
validate is a command published in the GitHub repository ankushdixit/claude-plugins (3 stars, last pushed 9mo ago), licensed MIT. It adds 9 tokens to every session and 194 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, revision-bound evidence, and PR-ready output.
red-team
Stress-test a plan, strategy, PRD, or launch with a room of hostile expert personas before you commit.
AGENTS
Run the current binary in a temporary test repository with a real PTY. Use tmux-cli when available, capture terminal output, and inspect -vv logs when behavior depends on timing or shell state. Avoid treating a piped command as proof of interactive behavior.
implement
Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.