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 jcarlosrodicio/opencode-agent-orchestration-kit --skill oak-enrich-taskgit clone --depth 1 https://github.com/jcarlosrodicio/opencode-agent-orchestration-kitWrote 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/jcarlosrodicio/opencode-agent-orchestration-kit/oak-enrich-task)<a href="https://agentmods.dev/skills/jcarlosrodicio/opencode-agent-orchestration-kit/oak-enrich-task"><img src="https://agentmods.dev/badge/skills/jcarlosrodicio/opencode-agent-orchestration-kit/oak-enrich-task/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/jcarlosrodicio/opencode-agent-orchestration-kit/oak-enrich-task"><img src="https://agentmods.dev/badge/skills/jcarlosrodicio/opencode-agent-orchestration-kit/oak-enrich-task.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.00061 | $0.00824 |
| Opus 5.5 | $0.00024 | $0.00330 |
| Sonnet 5.5 | $0.00012 | $0.00165 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
oak-enrich-task 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 17d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enrich Task
Overview
A short request hides most of the decisions an implementation needs. This skill turns it into a specification a developer can build and a reviewer can check, and it surfaces the questions the request does not answer instead of guessing.
The input can be a roadmap line, a phase name, free text, a screenshot or a link. Work from what was given. Do not ask for a ticket id and do not fetch one.
When to skip
Skip the skill when the request already states acceptance criteria, the files or modules it affects, and its non-functional requirements. Say that you skipped it and why.
If the request is larger than one reviewable change, stop and propose a split into smaller tasks instead of enriching the whole thing.
Steps
- Read the project's own rules first. Open the repository
AGENTS.mdand follow its links to the architecture, standards and data-model documents the task touches. Do this before exploring code. - Understand the problem before the solution. State who has the problem, what they cannot do today and what changes for them. Keep technical depth, but do not jump to an implementation.
- Find what to reuse. Name the existing endpoints, models, components, use cases and response shapes the change should build on. Reuse beats new code.
- Test for completeness. Check that the enhanced version covers:
- the behavior, including every field that changes;
- the boundaries the change may cross (modules, services, stored data);
- the definition of done, including doc and test updates;
- non-functional requirements: security, performance, observability and data integrity.
- Write the enhanced version in the format below.
- List the open questions. At minimum consider: one or many, who owns it, who may do it, what happens to existing data, and what happens on partial failure. Never answer one of these silently inside the requirements.
Output format
The output has exactly two top-level headings.
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.
- 17d ago First seen · 110 lines · 61 tokens per session scan A a13031f8a5d1
oak-enrich-task is a skill published in the GitHub repository jcarlosrodicio/opencode-agent-orchestration-kit (133 stars, last pushed 18d ago), licensed Apache-2.0. It adds 61 tokens to every session and 824 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-09-29.
Other skills, from other repositories
qa
Run scalable, isolated live QA for nac development. The top-level local orchestrator must parse n (default 4), dispatch one setup worker with this skill, copy its n assignment contracts verbatim into exactly n parallel test workers with this skill, then dispatch one aggregate worker with this skill using all test…
release
Cut and publish a full stable NAC release after main, release-PR, and publication CI pass. Use when a maintainer asks for a stable version bump, tag, or GitHub Release. Never use for release candidates; NAC RC releases are automated.
triage
Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…
ahk-test
Design, write, and run behavior-focused tests for an objective or existing code. Writes test files only and reports evidence. No tasks created, no harness tracking.
ahk-review
Preview a code review against ticket/objective alignment, with deep semantic (name-vs-behavior) analysis. No tasks created, no harness tracking.
ahk-consultant
Get technical advice or review on an approach, idea, or change. References available skills for best practices. No tasks created, no harness tracking.