OpenAgents Control is a framework that adds plan-first, approval-based coding workflows to OpenCode, an AI coding framework. Developers and teams use it to make agents follow shared coding patterns, work across several programming languages, and validate changes through testing and review. The catalogue includes its agents, skills, commands, plugin, and hook.
Borrowing it
Nothing to install: this file belongs to darrenhinde/OpenAgentsControl. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/darrenhinde/OpenAgentsControl/main/.opencode/skill/project-orchestration/SKILL.mdgit clone --depth 1 https://github.com/darrenhinde/OpenAgentsControlWrote 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/darrenhinde/openagentscontrol/project-orchestration)<a href="https://agentmods.dev/skills/darrenhinde/openagentscontrol/project-orchestration"><img src="https://agentmods.dev/badge/skills/darrenhinde/openagentscontrol/project-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/darrenhinde/openagentscontrol/project-orchestration"><img src="https://agentmods.dev/badge/skills/darrenhinde/openagentscontrol/project-orchestration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Agent Snooping · line 321 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.
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.00025 | $0.02445 |
| Opus 5.5 | $0.00010 | $0.00978 |
| Sonnet 5.5 | $0.00005 | $0.00489 |
| Haiku 4.5 | $0.00003 | $0.00245 |
Grade A, and why
project-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.
How it starts
The opening of the file, as written. The whole thing — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Orchestration Skill
Purpose: Orchestrate multi-agent workflows for feature development
What I Do
Coordinate multi-agent planning and execution workflows:
- Pass minimal context between planning agents
- Track planning agent outputs
- Manage 8-stage feature delivery workflow
- Maintain planning session state
Three Workflows
1. Context Handoff (Lightweight)
Pass minimal context between agents (RECOMMENDED for automation)
- Commands: create, get-context, add-output, show
- Use when: Orchestrating planning agents
- See: workflows/context-handoff.md
2. Session Context (Interactive)
Human-readable planning narrative (for debugging/review)
- Commands: session-create, session-load, session-summary
- Use when: Debugging or reviewing planning sessions
- See: workflows/context-handoff.md
3. Multi-Stage Delivery (8 Stages)
Full feature delivery workflow
- Commands: stage-init, stage-status, stage-complete, stage-rollback
- Use when: Running complete 8-stage feature workflow
- See: workflows/8-stage-delivery.md
Quick Start
Context Handoff Workflow
# Create context index
bash .opencode/skill/project-orchestration/router.sh create auth-system
# Get minimal context for specific agent
bash .opencode/skill/project-orchestration/router.sh get-context auth-system StoryMapper
# Track agent output
bash .opencode/skill/project-orchestration/router.sh add-output auth-system ArchitectureAnalyzer .tmp/architecture/auth-system/contexts.json
# Show full index
bash .opencode/skill/project-orchestration/router.sh show auth-system
8-Stage Workflow
# Initialize workflow
bash .opencode/skill/project-orchestration/router.sh stage-init auth-system
# Check status
bash .opencode/skill/project-orchestration/router.sh stage-status auth-system
# Mark stage complete
bash .opencode/skill/project-orchestration/router.sh stage-complete auth-system 1
# Rollback if needed
bash .opencode/skill/project-orchestration/router.sh stage-rollback auth-system 1
What ships with it
7 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.
- 1mo ago First seen · 324 lines · 25 tokens per session scan A e214bc14fca7
project-orchestration is a skill published in the GitHub repository darrenhinde/OpenAgentsControl (4,925 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 2,445 once invoked, about $0.0001 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-30.
Other skills, from other repositories
agent-orchestrator
Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
company-product-context
Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.
deep-researcher
Performs comprehensive, multi-layered research on any topic with structured analysis and synthesis of information from multiple sources.
codebase-context-extractor
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.
llmtornado-tutorial-generator
Generates comprehensive code tutorials on LlmTornado API formatted for Medium publication with examples, explanations, and best practices.
skill-creator
Generates Anthropic Skills with complete workflow including GitHub PR creation and local download verification.