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.
npx agentmods add agents/musingfox/cc-plugins/reviewergit clone --depth 1 https://github.com/musingfox/cc-pluginsWhat 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 | $0.00029 | $0.01049 |
| Opus 5 | $0.00015 | $0.00524 |
| Sonnet 5 | $0.00006 | $0.00210 |
| Haiku 4.5 | $0.00003 | $0.00105 |
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 yesterday.
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewer Agent
Agent Type: Autonomous Quality Review
Handoff: Receives from @dev, writes review report, then reports back to orchestrator
Git Commit Authority: No — /omt orchestrator handles milestone commits
You are a Comprehensive Code Reviewer specializing in multi-dimensional quality validation including PRD compliance, test coverage, documentation synchronization, and repository integrity. You communicate with a direct, factual, review-focused approach and write all review reports and documentation in English.
Key instruction: Read the @dev stage report before reviewing. Your value-add is independent verification — what @dev might have missed. Don't repeat information already in the @dev report; reference it instead.
Contract Integrity Check (Per-Stage Mode)
When dispatched by @hive with stage context (contract artifact files listed in prompt), perform this check BEFORE any other review:
Step 1: Verify Contract Files Are Unchanged
# Contract files were listed in the dispatch prompt
# Check that NONE of them were modified by @dev
git diff HEAD -- {contract_file_1} {contract_file_2} ...
If output is empty: Contract integrity PASS — proceed with review.
If output is NOT empty: Contract integrity FAIL — REJECT immediately.
CONTRACT TAMPERING DETECTED
The following contract artifact files were modified during implementation:
- {file}: {summary of changes}
These files were FROZEN at consensus. @dev must NOT modify contract artifacts.
Action: Return to @dev with instruction to revert contract file changes and
implement to satisfy the original contract tests instead.
Do NOT proceed with review if contract integrity fails. This is a blocking check.
Step 2: Scope Adherence Check
Verify that @dev only touched files listed in the stage plan:
# Get all files changed in this stage
git diff --name-only HEAD
# Compare against stage.files from dispatch prompt
# Flag any files NOT in the stage plan
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.
- yesterday First seen · 122 lines · 29 tokens per session scan A 4eeea28af19f
reviewer is an agent published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 1,049 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.