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/random6913/claude-code-superkit/dev-orchestratornpx skills add RaNDoM6913/claude-code-superkit --skill dev-orchestratorgit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWhat 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.00056 | $0.03785 |
| Opus 5 | $0.00028 | $0.01893 |
| Sonnet 5 | $0.00011 | $0.00757 |
| Haiku 4.5 | $0.00006 | $0.00379 |
Grade A, and why
dev-orchestrator scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| 1 | [specific, testable outcome] | [grep / curl / test / read] | Score >= 7 | MUST | How it starts
The opening of the file, as written. The whole thing — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Orchestrator
Run the full development cycle for the user's request as 16 numbered phases (0-15). You are the orchestrator AND the executor: Codex has no subagents, so wherever this skill says "perform X following the skill", read .codex/skills/<name>/SKILL.md and execute its process inline yourself, then apply its verdict exactly as that skill defines it.
Task
Parse the user's request to determine scope and parameters.
Hard Rules
- Execute phases in order 0 -> 15. Skip a phase ONLY when the Skip Matrix says so for the task's declared complexity class.
- A phase is complete only when its Done when condition holds. If a phase produces errors, fix them before advancing.
- Consume gate verdicts exactly as produced: plan-checker -> PASS/REVISE/BLOCK; evaluator -> PROCEED/ITERATE/ESCALATE; goal-verifier -> PASS/NEEDS-ATTENTION/NEEDS-REMEDIATION; critic -> APPROVE/CONCERN/BLOCK.
- Every gate is performed inline by following the named skill in
.codex/skills/<name>/SKILL.md. On a failed gate or retry, state what you are retrying and what changed since the last attempt -- never silently re-run the same approach. - Never claim completion while compilation or tests fail. The Phase 15 report is emitted only after every non-skipped phase has run.
- If the task is ambiguous, ask the user before Phase 7 (Implement) -- not after.
- Always read existing patterns before writing new code -- search first, reuse the closest implementation as reference.
Phase Overview & Skip Matrix
Complexity (Simple / Standard / Complex) is decided in Phase 1 and never changes mid-run.
| # | Phase | Simple | Standard | Complex | Gate skill |
|---|---|---|---|---|---|
| 0 | Read Docs | yes | yes | yes | - |
| 1 | Understand | yes | yes | yes | - |
| 2 | Architect | - | - | yes | architect |
| 3 | Pseudocode | - | - | yes | - |
| 4 | Plan | yes | yes | yes | - |
| 5 | Contract | - | yes | yes | - |
| 6 | Validate Plan | - | yes | yes | plan-checker |
| 7 | Implement | yes | yes | yes | - |
| 8 | Evaluate | - | yes (max 2 passes) | yes (max 3 passes) | evaluator |
| 9 | Verify | yes | yes | yes | health-checker |
| 10 | Test | yes | yes | yes | test-generator |
| 11 | Verify Goals | - | yes | yes | goal-verifier |
| 12 | Review | yes | yes | yes | reviewer skills |
| 13 | Critic | - | - | yes | critic |
| 14 | Document | yes | yes | yes | docs-reviewer |
| 15 | Report | yes | yes | yes | - |
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 · 307 lines · 56 tokens per session scan A a58ec2796a1b
dev-orchestrator is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 3,785 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
apm-review-panel
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
apm-spec-guardian
Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/.schema.json), or the conformance fixture seed…
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.
batch-bug-shepherd
Use this skill to drive a batch of suspected bugs in microsoft/apm from raw issue list to mergeable PR queue. Fan out one triage subagent per issue (LEGIT / UNCLEAR / FIXED-AT-HEAD), gate every legit bug against PRINCIPLES.md via an apm-ceo strategic-alignment pass, cross-reference legit issues against open PRs, then…
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…