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 skills/5uck1ess/devkit/mega-prnpx skills add 5uck1ess/devkit --skill mega-prgit clone --depth 1 https://github.com/5uck1ess/devkitWhat 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.00219 | $0.00571 |
| Opus 5 | $0.00110 | $0.00285 |
| Sonnet 5 | $0.00044 | $0.00114 |
| Haiku 4.5 | $0.00022 | $0.00057 |
Grade A, and why
mega-pr 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.
What it actually says
Mega PR Review
Run /devkit:tri-review and /pr-review-toolkit:review-pr simultaneously for maximum review coverage when those skills/plugins are available. Under non-Claude hosts, run devkit's tri-review MCP workflow and any available external review command; if pr-review-toolkit is not installed in the host, report that part as unavailable instead of fabricating results.
Step 1: Launch Both Reviews
[PARALLEL] — invoke both in a single message using the Skill tool:
Skill: devkit:tri-review— dispatches available model-diverse reviewersSkill: pr-review-toolkit:review-pr— dispatches specialized aspect reviewers when the Claude plugin is installed (silent-failure-hunter, type-design-analyzer, test-analyzer, code-reviewer, etc.)
Pass any user-provided arguments (custom prompt, specific files) to both skills unchanged.
Step 2: Present Combined Results
After both complete, present a unified report:
## Mega PR Review: <branch_name>
### tri-review Results
<consensus + unique findings>
### pr-review-toolkit Results
<categorized by severity>
### Summary
- Total agents participated: <count>
- Critical issues: <count>
- Warnings: <count>
- Suggestions: <count>
Rules
- Always run both in parallel — never sequential
- If one skill fails, still present the other's results
- Do not deduplicate — let the user see both perspectives
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 · 59 lines · 219 tokens per session scan A a19a0e256854
mega-pr is a skill published in the GitHub repository 5uck1ess/devkit (5 stars, last pushed 13d ago), licensed MIT. It adds 219 tokens to every session and 571 once invoked, about $0.0011 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
dynamic-workflows
Ultracode / Max-Parallel mode — dynamic workflows fan work out across tens–hundreds of adversarially-verified parallel subagents for large, decomposable jobs (codebase-wide audits, big migrations, cross-checked research). Opt-in; higher token spend.
cost-efficiency
Smart Routing — the DEFAULT CCGodMode routing policy. Risk-based, minimal-agent paths that preserve required safety gates for the changed scope.
agent-teams
Experimental Agent Teams orchestration — run CCGodMode agents as parallel teammates with SharedTaskList coordination (requires CLAUDECODEEXPERIMENTALAGENTTEAMS=1).
quality-gates
Parallel quality gate orchestration — @validator and @tester run simultaneously after @builder, with mandatory decision matrix for pass/fail routing.
sprint-planning
Plan-first orchestration (ADR-004): comprehensive PLAN.md, sprint files with write-scope ownership, preflight checks, serialized integration, and the release sprint. Use for any non-trivial or multi-part request BEFORE dispatching agents.
workflows
CCGodMode Full-Gates workflow definitions — used for high-risk work and when Smart Routing escalates. Default routing is Smart Routing (skills/cost-efficiency/).