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 skills add euxx/claude-skills-for-copilot --skill review-toolkitgit clone --depth 1 https://github.com/euxx/claude-skills-for-copilotWrote 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/skills/euxx/claude-skills-for-copilot/review-toolkit)<a href="https://agentmods.dev/skills/euxx/claude-skills-for-copilot/review-toolkit"><img src="https://agentmods.dev/badge/skills/euxx/claude-skills-for-copilot/review-toolkit/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/skills/euxx/claude-skills-for-copilot/review-toolkit"><img src="https://agentmods.dev/badge/skills/euxx/claude-skills-for-copilot/review-toolkit.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.00066 | $0.00552 |
| Opus 5 | $0.00033 | $0.00276 |
| Sonnet 5 | $0.00013 | $0.00110 |
| Haiku 4.5 | $0.00007 | $0.00055 |
Grade A, and why
review-toolkit 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 11d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Toolkit
Comprehensive code review orchestrator. Dispatches specialist review agents based on the scope of changes and aggregates all findings in a unified report.
Specialist Skills
| Skill | Purpose |
|---|---|
| code-review | Bugs, security issues, correctness, conventions-file violations |
| code-simplifier | Unnecessary complexity, duplication, readability |
| comment-analyzer | Comment accuracy, comment rot, misleading documentation |
| silent-failure-hunter | Silent errors, inadequate user feedback, catch block quality |
| type-design-analyzer | Type encapsulation, invariant expression and enforcement |
| test-analyzer | Behavioral coverage gaps, test quality, anti-pattern detection |
Dispatch Rules
Always run:
- code-review — applies to any code change
Run when applicable:
- test-analyzer — test files modified or new behavior added
- silent-failure-hunter — error handling code modified (
try/catch, error callbacks, fallbacks) - type-design-analyzer — new types, interfaces, or data models added or significantly changed
- comment-analyzer — documentation comments or inline comments added/modified
Run after correctness is confirmed (regardless of other findings):
- code-simplifier — once critical bugs and coverage gaps are resolved
Process
- Identify the scope of changes (files changed, types of changes)
- Determine which specialist skills to dispatch based on the rules above
- Run each selected skill as a sub-agent against the relevant scope
- Collect all findings
- Aggregate into a unified report
Output Format
## Toolkit Summary
Specialists dispatched: [list]
Overall assessment: [PASS / NEEDS WORK / CRITICAL ISSUES]
## Critical Issues
[Aggregated CRITICAL findings from all specialists, with source skill noted]
## Important Issues
[Aggregated HIGH/IMPORTANT findings]
## Suggestions
[Aggregated MEDIUM/lower priority findings]
## Positive Observations
[Notable good practices found across all reviews]
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.
- 11d ago First seen · 69 lines · 66 tokens per session scan A f07997dbc4b7
review-toolkit is a skill published in the GitHub repository euxx/claude-skills-for-copilot (4 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 552 once invoked, about $0.0003 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 skills, from other repositories
pr-comment-review
Audit and remediate an open GitHub PR's review feedback: verify Copilot and Codex actually reviewed, drive every unresolved thread to a fix-or-justify reply, correct PR title/description drift against the real diff, and run a one-time self-review pass. Trigger on "have all PR comments been addressed", "did copilot and…
audit-legacy-controller
Read the legacy Admin{Domain}sController.php without modifying it. Extract every field rendered, every action method, and every Hook::exec() call.
copilot-mcp-server
Direct access to GitHub Copilot MCP server tools for AI-powered development assistance.
continual-learning
Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt…
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.