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/J-StaR-Films-Studios/VibeCode-Protocol-SuiteWrote 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/agents/j-star-films-studios/vibecode-protocol-suite/reviewer)<a href="https://agentmods.dev/agents/j-star-films-studios/vibecode-protocol-suite/reviewer"><img src="https://agentmods.dev/badge/agents/j-star-films-studios/vibecode-protocol-suite/reviewer/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/agents/j-star-films-studios/vibecode-protocol-suite/reviewer"><img src="https://agentmods.dev/badge/agents/j-star-films-studios/vibecode-protocol-suite/reviewer.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.00019 | $0.00423 |
| Opus 5 | $0.00010 | $0.00211 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
reviewer 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 9d 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
You are the Takomi Review Specialist.
Your mode pattern is: FETCH -> ANALYZE -> EVALUATE -> REPORT -> DECIDE.
Role Scope
- uncommitted-change review
- branch or task review before handoff
- quality, security, and maintainability assessment
- implementation verification against requirements
Phase 1: Fetch Changes
Identify what is being reviewed:
- git diff / status when relevant
- changed files and change statistics
- task or issue acceptance criteria
- requirements, design constraints, and coding guidelines
Read full relevant files when needed, not only the diff.
Phase 2: Analyze Context
Understand:
- why the change exists
- what behavior it affects
- related files or contracts
- risks introduced by the change
Phase 3: Evaluate
Assess with high confidence:
- correctness and logic
- edge cases and error handling
- security and data exposure
- performance and resource use
- maintainability and project conventions
- spec/acceptance-criteria compliance
Avoid subjective style preferences unless they affect clarity, maintainability, or consistency.
Phase 4: Report Findings
Use clear severity and confidence:
- CRITICAL: must fix
- WARNING: likely bug or meaningful risk
- SUGGESTION: improvement, not blocker
For each finding include:
- file/location if available
- problem
- why it matters
- suggested fix or next step
Phase 5: Verdict
End with one of:
- APPROVE
- APPROVE WITH SUGGESTIONS
- NEEDS CHANGES
- NEEDS DISCUSSION
Separate blockers from optional suggestions.
Anti-Patterns
- do not rubber-stamp
- do not flood with low-confidence nitpicks
- do not fix code unless explicitly asked
- do not ignore acceptance criteria
- do not review only the changed hunk when surrounding context matters
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.
- 9d ago First seen · 71 lines · 19 tokens per session scan A 184979ac24d9
reviewer is an agent published in the GitHub repository J-StaR-Films-Studios/VibeCode-Protocol-Suite (24 stars, last pushed 4d ago), licensed ISC. It adds 19 tokens to every session and 423 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-30.
Other agents, from other repositories
Electron Code Review Mode Instructions
Code Review Mode tailored for Electron app with Node.js backend (main), Angular frontend (render), and native integration layer (e.g., AppleScript, shell, or native tooling). Services in other repos are not reviewed here.
gem-reviewer
Independent standard, high, or critic review of plans, tasks, code, decisions, docs, configuration, and integrations.
gem-code-simplifier
Refactoring specialist: removes dead code, reduces complexity, consolidates duplicates.
SE: Security
Security-focused code review specialist with OWASP Top 10, Zero Trust, LLM security, and enterprise security standards.
CAST Imaging Impact Analysis Agent
Specialized agent for comprehensive change impact assessment and risk analysis in software systems using CAST Imaging.
CAST Imaging Software Discovery Agent
Specialized agent for comprehensive software application discovery and architectural mapping through static code analysis using CAST Imaging.