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/dzan314/yapperWrote 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/dzan314/yapper/yapper-review)<a href="https://agentmods.dev/commands/dzan314/yapper/yapper-review"><img src="https://agentmods.dev/badge/commands/dzan314/yapper/yapper-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/dzan314/yapper/yapper-review"><img src="https://agentmods.dev/badge/commands/dzan314/yapper/yapper-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.00000 | $0.01129 |
| Opus 5.5 | $0.00000 | $0.00452 |
| Sonnet 5.5 | $0.00000 | $0.00226 |
| Haiku 4.5 | $0.00000 | $0.00113 |
Grade A, and why
yapper-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 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.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/yapper-review Command
Description
The /yapper-review command performs a thorough, multi-line pull request review.
Rather than posting terse inline comments like "this is wrong" or "use X instead,"
yapper-review produces fully-explained feedback that describes the issue, the reasoning
behind the concern, the potential impact, and a concrete suggested fix — complete with
explanation of why the fix addresses the underlying problem.
Usage
/yapper-review [paste PR diff or describe PR]
/yapper-review --url [GitHub PR URL, if integration available]
/yapper-review --file [filename]
Output Format
For each issue identified, the review MUST produce the following structure:
🔍 Issue: [Short descriptive title]
Location: filename.ext, line N (or general section)
Severity: [Critical / Major / Minor / Suggestion]
What the issue is:
[A full paragraph describing what was observed in the code and why it constitutes an issue. Be specific. Quote the relevant line or pattern if helpful.]
Why this matters:
[A full paragraph explaining the potential consequences of this issue. What could go wrong? Under what conditions? How likely is it? Who is affected?]
Suggested fix:
[Code block showing the suggested correction, followed by a prose explanation of why this fix addresses the root cause — not just the symptom.]
// suggested code here
[Explanation of what the fix does differently and why that resolves the issue.]
Additional context:
[Any relevant background, links to documentation, related patterns, or follow-up work that might be warranted.]
Rules
-
Every issue must include all five sections: what, why, fix, explanation of fix, and additional context
-
No comment may be a single sentence. The minimum length for any review comment is three full sentences.
-
The suggested fix must be accompanied by an explanation of why it works, not just what it does
-
Severity levels must be used accurately:
- Critical: Will cause production failures, security vulnerabilities, or data loss
- Major: Likely to cause bugs, performance issues, or maintainability problems
- Minor: Code quality, convention violations, or suboptimal patterns
- Suggestion: Optional improvements worth considering
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 · 144 lines · 0 tokens per session scan A bd38b4606780
yapper-review is a command published in the GitHub repository dzan314/yapper (1 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,129 tokens. 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
ia-verify
Run pre-PR verification chain: build, types, lint, tests, security scan, diff review.
check-architecture
Angular Architecture Review.
announce
Draft X/Twitter announcement post (or thread) for the latest plugin release.
review
Review code across five axes with categorized findings.
cg-senior-code-review
Perform deep, findings-first senior engineering code reviews of any change in any language or stack. Use when reviewing a phase, feature branch, pull request, commit, or uncommitted changes for correctness bugs, security and abuse risks, regressions to existing behavior, concurrency and lifecycle defects, performance…
create-pr
Create a Pull Request from the current branch targeting develop, with correct PRJ-XXX title format, Jira link in the body, and optional Jira status sync.