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/kastheco/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/kastheco/claude-plugins/review-reality)<a href="https://agentmods.dev/commands/kastheco/claude-plugins/review-reality"><img src="https://agentmods.dev/badge/commands/kastheco/claude-plugins/review-reality.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.00009 | $0.00247 |
| Opus 5 | $0.00005 | $0.00123 |
| Sonnet 5 | $0.00002 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
review-reality 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 6d 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
/kas:review-reality - Reality Assessment
Validate claimed completions with extreme skepticism. Cut through optimistic status reports.
Workflow
1. Identify scope
git status
git diff --stat
If no changes, report "Nothing to assess" and stop.
2. Read agent instructions
Read agents/project-reality-manager.md (relative to plugin root) and apply the reality assessment approach defined there.
3. Execute assessment
Assess with skepticism:
- What actually works when tested vs what merely exists in code
- Functions that exist but don't work end-to-end
- Missing error handling that makes features unusable
- Gaps between claimed and actual completion
4. Return findings
Provide structured output with:
- Honest assessment of current functional state
- Gap analysis with severity (Critical / High / Medium / Low)
- Prioritized action plan with testable completion criteria
- Prevention recommendations
Rules
- Read-only: Never edit files
- Verify before trusting - test actual functionality
- Zero tolerance for optimistic status reports
- Return findings, do not apply fixes
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.
- 6d ago First seen · 46 lines · 9 tokens per session scan A cc2effb33834
review-reality is a command published in the GitHub repository kastheco/claude-plugins (2 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 247 once invoked, about $0.0000 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-31.
Other commands, from other repositories
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
timeout-fix
A procedure for diagnosing and fixing tests that exceed their time limit by finding causes such as slow processing, hanging network calls, deadlocks, heavy setup, or leaked resources.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.