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/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/validation-plan)<a href="https://agentmods.dev/commands/kensaurus/cursor-kenji/validation-plan"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/validation-plan.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.1 | $0.00016 | $0.00149 |
| Opus 5 | $0.00008 | $0.00075 |
| Sonnet 5 | $0.00003 | $0.00030 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
validation-plan 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 3d 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
Input Validation Plan
Run the plan-input-validation skill: audit every trust boundary
(forms/API, rendered content, webhooks, uploads) for unvalidated input, then
produce a hardening plan. Audit and plan only — add no validation until the
plan is approved.
Emit findings ranked by severity with concrete file:line locations and a
phased hardening checklist. After approval, execute with backend-patterns and
backend-error-handling.
The full playbook lives in the plan-input-validation skill.
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.
- 3d ago First seen · 18 lines · 16 tokens per session scan A b037c73f4fe6
validation-plan is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 9d ago), licensed MIT. It adds 16 tokens to every session and 149 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-09-03.
Other commands, from other repositories
update-issue
Update an issue description with structured, evidence-backed content.
next-task
Intelligently determine and prepare the next action based on comprehensive context.
parse-prd
Command "parse-prd" from eyaltoledano/claude-task-master, covering intelligent prd parsing, execution, parsing process, options and post-generation.
setup-models
Run interactive setup to configure AI models.
to-review
Command "to-review" from eyaltoledano/claude-task-master, covering marking task for review, when to use review status, execution and review preparation.
quick-install-taskmaster
Quick install Task Master globally if not already installed.