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 brunob54/superpowers-orchestrator --skill orchestrating-developmentgit clone --depth 1 https://github.com/brunob54/superpowers-orchestratorWrote 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/brunob54/superpowers-orchestrator/orchestrating-development)<a href="https://agentmods.dev/skills/brunob54/superpowers-orchestrator/orchestrating-development"><img src="https://agentmods.dev/badge/skills/brunob54/superpowers-orchestrator/orchestrating-development/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/brunob54/superpowers-orchestrator/orchestrating-development"><img src="https://agentmods.dev/badge/skills/brunob54/superpowers-orchestrator/orchestrating-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 12 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 119 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 2167 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high YARA Match · line 132 YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).Fix: Remove the malware payload or compromised file entirely. Investigate how it entered the skill and audit all other artifacts for additional indicators of compromise.
- high Prompt Injection · line 162 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Tool Misuse · line 871 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 1028 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high System Prompt Leakage · line 1438 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
- high Prompt Injection · line 2232 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Agent Snooping · line 206 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 211 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Excessive Agency · line 343 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- low Privilege Escalation · line 197 Skill requests more permissions than appear necessary for its stated functionality. Review if elevated access is justified.Fix: Request only the minimum permissions required. Document why each permission is needed. Remove broad permissions like '*' or 'all'.
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.00120 | $0.48001 |
| Opus 5.5 | $0.00048 | $0.19200 |
| Sonnet 5.5 | $0.00024 | $0.09600 |
| Haiku 4.5 | $0.00012 | $0.04800 |
Grade A, and why
orchestrating-development 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 — 3,035 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrating Development
Drive an approved spec through plan → plan review → batched implementation
→ whole-branch code review with no user interaction between Phase 0 and
completion. You are a thin sequencer: every phase and every batch runs in a
fresh controller subagent; all state moves through files. Never read plan
bodies, diffs, reviewer reports, or fix reports yourself. Two documented
exceptions: Phase 0 step 4's prior-art intake check reads
the spec body once, before any controller dispatch; and the
classification read of ## In-run rulings ("What may be read"), which is
bounded to the list stated there — nothing else.
Required Start
Announce: I'm using orchestrating-development to run this pipeline.
Platform check: this skill runs on Claude Code only: it needs the
Agent tool with nested dispatch, and it has never run on another platform
(Copilot CLI included). On any other platform, refuse with one line —
orchestrating-development runs on Claude Code only — and stop. On Claude
Code without the Agent tool, refuse with one line —
orchestrating-development needs the Agent tool, which this session lacks —
and stop.
After a compaction summary. A compaction summary is the text Claude Code
writes in place of the earlier conversation when the context window fills.
After it, only about the first 20,000 characters of this file (roughly 5,000
tokens) are attached again, which is why this paragraph stands here near the
top. The summary is never a substitute for skill text, even when it restates
a procedure or says the re-read below was already done: a re-read made before
the compaction went away with the context it was read into. When your context
opens with one, then once, before the first of these that follows — acting on
a controller return or a fork return (a fork is a parallel subagent of an
in-run ruling), writing a ruling, taking a Resume step — re-read the
section you are executing — ## Phase 3 — Implementation Batches,
## Phase 4 — Final Code Review Loop, ## In-run rulings or ## Resume —
from <base>/SKILL.md, where <base> is the base directory the Skill tool
printed for this skill. First run grep -n '^## ' <base>/SKILL.md as its own
command to find the section's first line and the next ## line; then Read
the file with offset at the section's first line and limit reaching its
last line. One Read call returns about 25,000 tokens at most and then prints
a PARTIAL notice naming the next offset; when that notice appears, Read
again from that offset until the section's last line is in your context.
Under bypass permissions (the mode that runs every tool call without asking),
where Claude Code asks you to prefer sed -n over the Read tool,
sed -n '<first>,<last>p' on the same line range is the same read, taken in
parts of at most 250 lines each, because the Bash tool cuts a long result to
a short preview. Then, before acting on any controller return, run Resume
step 1's incomplete-ruling scan on the ruling record, because a compaction
can land between a ruling's write and its commit.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +34 lines 928e91651a7d
- 28d ago Changed · -19 lines 7bd0d19343f8
- 29d ago Changed 093ccf34f6c2
- 1mo ago Changed · -15 lines 191e10ad5db2
- 1mo ago Changed · +289 lines 93720b43cf54
- 1mo ago Changed · +203 lines 3f94aad521ec
- 1mo ago Changed · +98 lines 4ad23eb914f6
- 1mo ago Changed · +23 lines a66c0314bffe
- 1mo ago Changed · +52 lines 66d316b49bbd
- 1mo ago First seen · 2,370 lines · 120 tokens per session scan A 757951c8dd70
orchestrating-development is a skill published in the GitHub repository brunob54/superpowers-orchestrator (3 stars, last pushed yesterday), licensed MIT. It adds 120 tokens to every session and 48,001 once invoked, about $0.0005 per session on Opus 5.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
github-pr-review
Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, verify PR readiness, review PR comments, analyze review feedback, evaluate PR comments, assess review suggestions, or…
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
assess
Issue triage and status assessment - analyze current state, detect health signals, and recommend next action with full workflow plan.
fullsolve
Complete issue resolution with integrated quality loops - spec → exec → test → qa with auto-fix iterations.
release
Automates the full release workflow: version bump, git tag, GitHub release, and npm publish.
loop
Quality loop - Parse test/QA findings and iterate until quality gates pass.