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 ArtemioPadilla/agent-triforce --skill subagent-orchestrationgit clone --depth 1 https://github.com/ArtemioPadilla/agent-triforceWrote 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/artemiopadilla/agent-triforce/subagent-orchestration)<a href="https://agentmods.dev/skills/artemiopadilla/agent-triforce/subagent-orchestration"><img src="https://agentmods.dev/badge/skills/artemiopadilla/agent-triforce/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/artemiopadilla/agent-triforce/subagent-orchestration"><img src="https://agentmods.dev/badge/skills/artemiopadilla/agent-triforce/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.00044 | $0.00541 |
| Opus 5.5 | $0.00018 | $0.00216 |
| Sonnet 5.5 | $0.00009 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
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 1mo 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.
What it actually says
Subagent Orchestration
Execute the plan at: $ARGUMENTS
Process
- Read the plan file — extract all tasks with full text
- Create task tracking — one todo per task
- For each task:
a. Select model tier based on task complexity (see Model Selection below)
b. Dispatch implementer subagent using
.claude/agents/forja-prompts/implementer-prompt.mdc. Handle implementer status (DONE / DONE_WITH_CONCERNS / NEEDS_CONTEXT / BLOCKED) d. Dispatch spec-reviewer subagent using.claude/agents/forja-prompts/spec-reviewer-prompt.mde. If spec review fails: implementer fixes, re-review (loop until PASS) f. Dispatch code-quality-reviewer subagent using.claude/agents/forja-prompts/code-quality-reviewer-prompt.mdg. If quality review fails: implementer fixes Critical/Important issues, re-review h. Mark task complete - After all tasks: run full test suite, verify everything works together
Model Selection
| Task Signals | Model | Examples |
|---|---|---|
| 1-2 files, complete spec, mechanical | haiku |
Add a field, write a test, rename |
| Multi-file, integration, judgment needed | sonnet |
Wire up endpoint, refactor module |
| Architecture, design, broad codebase | opus |
Design subsystem, complex debug |
Subagent Dispatch Rules
- Sequential only for implementation subagents (avoids file conflicts)
- Spec review before code quality review (order matters)
- Review loops repeat until approved — no "close enough"
- Never make subagents read the plan file — provide full task text in the prompt
- If implementer asks questions: answer clearly, then re-dispatch
- If implementer is BLOCKED: assess and escalate (don't retry blindly)
Red Flags
- Starting code quality review before spec compliance passes
- Dispatching multiple implementers in parallel
- Ignoring DONE_WITH_CONCERNS status
- Skipping re-review after implementer fixes
- Forcing retry without changing context, model, or task scope
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.
- 1mo ago First seen · 52 lines · 44 tokens per session scan A ea81eb066f86
subagent-orchestration is a skill published in the GitHub repository ArtemioPadilla/agent-triforce (3 stars, last pushed 6mo ago), licensed MIT. It adds 44 tokens to every session and 541 once invoked, about $0.0002 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
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
cost-model
Standardized cost-estimation framework for greatcto plans. Forces explicit LLM cost, infra cost, human-supervision time, and the (defensible) human-equivalent comparison. Output format is parsable by the board's /api/cost path — must follow exactly.
deploy-landed
A deployment verification procedure that checks whether the intended code revision is actually running, its environment settings are present, and the product works. A deployment is the process of putting new software on a server or hosting platform.
stack-baseline
The pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability…
pm
Project manager for GitHub issues: brainstorm design approaches, create structured issues optimized for LLM agent teams, triage and recommend what to work on next, audit and clean up stale issues, or deep-validate a single issue against the codebase. Triggers: create issue, plan work, new task, project manager, write…