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/MadeByTokens/claude-code-plugins-madebytokensWrote 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/madebytokens/claude-code-plugins-madebytokens/review)<a href="https://agentmods.dev/commands/madebytokens/claude-code-plugins-madebytokens/review"><img src="https://agentmods.dev/badge/commands/madebytokens/claude-code-plugins-madebytokens/review/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/madebytokens/claude-code-plugins-madebytokens/review"><img src="https://agentmods.dev/badge/commands/madebytokens/claude-code-plugins-madebytokens/review.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.00018 | $0.01571 |
| Opus 5 | $0.00009 | $0.00785 |
| Sonnet 5 | $0.00004 | $0.00314 |
| Haiku 4.5 | $0.00002 | $0.00157 |
Grade A, and why
review 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.
How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Review
The user wants a comprehensive review of their PRD to identify gaps and issues.
Actions
- Read the entire session file
- Analyze each section for completeness
- Check for common issues
- Present findings with recommendations
Review Checklist
For each section, check:
Vision & Principles (CRITICAL - Taste Layer)
- Product vision clearly articulated in one sentence?
- Non-negotiable design principles listed?
- "What would feel wrong" documented?
- Aesthetic/UX north star defined?
- Explicit taste decisions recorded with rationale?
- Products admired for similar feel identified?
Problem Statement
- Background context provided?
- Specific pain points listed?
- Impact quantified or described?
- Current state explained?
Target Users
- At least one persona defined?
- Demographics included?
- Goals and frustrations listed?
- Behaviors described?
User Stories
- Follows "As a... I want... So that..." format?
- Each story has acceptance criteria?
- Priority assigned (Must/Should/Could/Won't)?
- No vague language?
Functional Requirements
- Specific and measurable?
- Prioritized?
- No implementation details (just WHAT, not HOW)?
Non-Functional Requirements
- Performance targets specified?
- Security requirements listed?
- Accessibility level defined (WCAG)?
- Scalability targets?
Data Model
- Key entities identified?
- Relationships described?
- Data constraints noted?
UI/UX Specification
- Key screens/flows identified?
- User flow described?
- Interaction patterns noted?
API Contract (if applicable)
- Endpoints listed?
- Request/response formats?
- Error handling?
Change Analysis (CRITICAL - Prevents Accidental Architecture)
- Configuration vs hardcode decisions documented?
- Flexibility requirements identified?
- Feature flags/toggle points considered?
- "What will likely change?" answered for each component?
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 · 243 lines · 18 tokens per session scan A 44727eb83f99
review is a command published in the GitHub repository MadeByTokens/claude-code-plugins-madebytokens (2 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 1,571 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.