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 Hipson47/Hipson --skill hipson-subagent-orchestrationgit clone --depth 1 https://github.com/Hipson47/HipsonWrote 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/hipson47/hipson/hipson-subagent-orchestration)<a href="https://agentmods.dev/skills/hipson47/hipson/hipson-subagent-orchestration"><img src="https://agentmods.dev/badge/skills/hipson47/hipson/hipson-subagent-orchestration/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/hipson47/hipson/hipson-subagent-orchestration"><img src="https://agentmods.dev/badge/skills/hipson47/hipson/hipson-subagent-orchestration.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.00048 | $0.00508 |
| Opus 5 | $0.00024 | $0.00254 |
| Sonnet 5 | $0.00010 | $0.00102 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
hipson-subagent-orchestration 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 9d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hipson Subagent Orchestration
Use this skill when the user asks for subagents, delegation, parallel agents, independent review, or when Hipson/global instructions explicitly authorize bounded subagent use for a non-trivial engineering task.
Core Contract
- The main Codex agent owns planning, delegation, integration, verification, and final judgment.
- Spawn subagents only for concrete work that can run independently and materially improve quality or speed.
- Prefer read-only
exploreragents for codebase mapping, risk discovery, test-gap analysis, logs, and research. - Use
workeragents only when the write scope is clear, bounded, and disjoint from other work. - Use one independent reviewer after meaningful changes when correctness, safety, or regression risk is non-trivial.
- Do not delegate tiny one-file fixes, urgent critical-path blockers, or overlapping edits.
- Treat subagent output as advice until verified against files, diffs, commands, or screenshots.
- Close completed or abandoned subagent threads after their results have been integrated.
Quick Workflow
- Decide what the main agent should do locally first.
- Split only parallelizable work into bounded subtasks.
- Give each subagent role, goal, repo path, files to inspect, constraints, write scope if any, verification expectations, and exact output format.
- Keep
fork_context=falseby default; pass a compact task packet instead of the whole thread. - Continue local non-overlapping work while subagents run.
- Wait only when the result blocks the next step.
- Review returned evidence, integrate useful findings, run final verification locally, and report what was verified.
Role Defaults
explorer: read-heavy discovery. No edits. Must cite files, commands, or observed evidence.worker: focused implementation. Must own a disjoint write scope and report files changed plus verification.defaultreviewer: read-only critique. Findings first, ordered by severity, with file/line evidence where possible.
What ships with it
1 file 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.
- 9d ago First seen · 40 lines · 48 tokens per session scan A e27386f87a61
hipson-subagent-orchestration is a skill published in the GitHub repository Hipson47/Hipson (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 48 tokens to every session and 508 once invoked, about $0.0002 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
sc-skill
Capture deterministic macOS screenshots for testing, docs, release notes, and marketing assets. Use when asked to automate app screenshots, batch-generate screenshot sets, standardize window sizing/composition, or choose between Peekaboo and native macOS screenshot tooling.
handover
Use when wrapping up or capturing the current state of a coding session — writes a short, dated entry to the repo's RepoHandover.md so a future agent or you can resume without grepping archived sessions. Triggers on "handover", "hand off", "write handover", "capture state", "checkpoint this session".
agent-session-format-check
Verify agent session format compatibility for Agent Sessions. Use when any agent CLI updates, when monitoring flags drift, or when bumping max verified versions (fixtures + docs + tests). Covers session schema, usage/limits tracking, storage backends, and discovery path contracts for all supported agents.
agent-support-matrix
Maintain Agent Sessions agent support matrix and JSON/JSONL parsing compatibility. Use when checking upstream agent releases for session format changes, updating max verified versions in docs/agent-support/agent-support-matrix.yml, or updating docs/agent-json-tracking.md and fixtures/tests.
kirby-collections-and-navigation
Builds Kirby listings, pagination, search, filtering/sorting/grouping, and navigation menus. Use when implementing collection logic in templates/controllers/snippets.
kirby-debugging-and-tracing
Diagnoses Kirby rendering/runtime issues using MCP runtime rendering, dump traces, and template/snippet/controller indexes. Use when outputs are wrong, errors occur, or tracing execution paths is required.