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/skills/task-management/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/task-management)<a href="https://agentmods.dev/skills/darrenhinde/openagentscontrol/task-management"><img src="https://agentmods.dev/badge/skills/darrenhinde/openagentscontrol/task-management/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/task-management"><img src="https://agentmods.dev/badge/skills/darrenhinde/openagentscontrol/task-management.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 395 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.00020 | $0.02492 |
| Opus 5.5 | $0.00008 | $0.00997 |
| Sonnet 5.5 | $0.00004 | $0.00498 |
| Haiku 4.5 | $0.00002 | $0.00249 |
Grade A, and why
task-management 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- task-management — 100% identical, 0 lines differ
- task-management — 100% identical, 0 lines differ
- task-management — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Management Skill
Purpose: Track, manage, and validate feature implementations with atomic task breakdowns, dependency resolution, and progress monitoring.
What I Do
I provide a command-line interface for managing task breakdowns created by the TaskManager subagent. I help you:
- Track progress - See status of all features and their subtasks
- Find next tasks - Show eligible tasks (dependencies satisfied)
- Identify blocked tasks - See what's blocked and why
- Manage completion - Mark subtasks as complete with summaries
- Validate integrity - Check JSON files and dependency trees
How to Use Me
Quick Start
# Show all task statuses
bash .opencode/skills/task-management/router.sh status
# Show next eligible tasks
bash .opencode/skills/task-management/router.sh next
# Show blocked tasks
bash .opencode/skills/task-management/router.sh blocked
# Mark a task complete
bash .opencode/skills/task-management/router.sh complete <feature> <seq> "summary"
# Validate all tasks
bash .opencode/skills/task-management/router.sh validate
Command Reference
| Command | Description |
|---|---|
status [feature] |
Show task status summary for all features or specific one |
next [feature] |
Show next eligible tasks (dependencies satisfied) |
parallel [feature] |
Show parallelizable tasks ready to run |
deps <feature> <seq> |
Show dependency tree for a specific subtask |
blocked [feature] |
Show blocked tasks and why |
complete <feature> <seq> "summary" |
Mark subtask complete with summary |
validate [feature] |
Validate JSON files and dependencies |
help |
Show help message |
Examples
Check Overall Progress
$ bash .opencode/skills/task-management/router.sh status
[my-feature] My Feature Implementation
Status: active | Progress: 45% (5/11)
Pending: 3 | In Progress: 2 | Completed: 5 | Blocked: 1
Find What's Next
$ bash .opencode/skills/task-management/router.sh next
=== Ready Tasks (deps satisfied) ===
[my-feature]
06 - Implement API endpoint [sequential]
08 - Write unit tests [parallel]
What ships with it
2 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 · 400 lines · 20 tokens per session scan A d0b914729a2f
task-management is a skill published in the GitHub repository darrenhinde/OpenAgentsControl (4,925 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 2,492 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
task-management
Task management CLI for tracking and managing feature subtasks with status, dependencies, and validation.
full-sdc
EXECUTE lean Full Story Development Cycle for one story: plan via CLI, run validate → develop → review (QG loop) → close with Sequence Lock, durable progress under .aiox/sdc/. Use when: full-sdc, full cycle, SDC, run story end-to-end.
wave-execute
EXECUTE a lean wave — plan story DAG + file-ownership batches via CLI, dispatch full-sdc per story, fan-in check, hand off merge to @devops. Use when: wave-execute, run wave, epic wave, parallel stories SDC.
close-story
Finalize bookkeeping for a story already completed by QA. Never changes lifecycle status. Use when: close story, close-story, story Done, /close-story.
develop-story
Implement a story (Ready → InProgress → ready for review). Runs the OSS develop task. Use when: develop story, develop, /develop-story, implement ACs.
review-story
QA gate for a story — verdict PASS/CONCERNS/FAIL/WAIVED + lifecycle transition. Use when: review story, qa gate, qa-gate, /review-story.