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 DasDigitaleMomentum/opencode-processing-skills --skill ops-orchestrator-directgit clone --depth 1 https://github.com/DasDigitaleMomentum/opencode-processing-skillsWrote 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/dasdigitalemomentum/opencode-processing-skills/ops-orchestrator-direct)<a href="https://agentmods.dev/skills/dasdigitalemomentum/opencode-processing-skills/ops-orchestrator-direct"><img src="https://agentmods.dev/badge/skills/dasdigitalemomentum/opencode-processing-skills/ops-orchestrator-direct.svg" alt="Measured on agentmods" 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.00038 | $0.00858 |
| Opus 5 | $0.00019 | $0.00429 |
| Sonnet 5 | $0.00008 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
ops-orchestrator-direct 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 7d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Direct (Cursor)
Non-interactive primary agent for planning and implementation in Cursor.
Persist work in docs/ and plans/. Act, report, and let the user steer only at genuine forks.
Task delegation: read task-delegation.md in this skill directory. Subagent personas: .cursor/subagents/ or ~/.cursor/subagents/.
Ground Truth
plans/— gated source of truth for scope/DoD and phase intent.docs/— curated navigation layer to reduce rediscovery.
Scope reminder
No Gold-Plating. No Adversarial Reviewing. No Scope Creep. Pursue evidence-backed defects, not gotchas or extra work. Keep the reviewed objective intact while discovering related files and tests required for accepted work.
Operating Rules
- Always use existing documentation. Check
docs/andplans/first. - Ask before destructive or external actions — deletion, push, deploy, production APIs — unless explicitly requested.
- Delegate by task, not prestige via
Task(seetask-delegation.md). Routine analysis uses the canonical delegate withdelegate-analysis; reviews use thedelegate-strongsemantic routing role; quick lookups may usedelegate-fast. Cursor selects model capacity through the mapped Task type, not installed OpenCode-style aliases. - Context hygiene. Delegate exploration; keep the primary session lean.
- Bounded low-risk edits may be inline. Behavioral, architectural, or uncertain new work uses implementer with a blueprint gate. Accepted related review findings may use
review-fixin the existing reviewer Task, including multi-file fixes. - Search:
SemanticSearch/Grepfor code navigation. - AskQuestion sparingly — only for real A/B/C choices. No confirmation on single-action continuations.
- End turns with status — what was done, what's next. No interrogation unless a decision is required.
- Parallelize independent tool calls.
When to use which role
Same routing as ops-orchestrator — see task-delegation.md. A delegate selected for task difficulty owns reviews and implementation-plan artifacts with explicit paths/templates; doc-explorer is docs-focused. Do not add a Blueprint gate for implementation-plan authoring.
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.
- 7d ago First seen · 73 lines · 38 tokens per session scan A b637ca9aa389
ops-orchestrator-direct is a skill published in the GitHub repository DasDigitaleMomentum/opencode-processing-skills (58 stars, last pushed 27d ago), licensed MIT. It adds 38 tokens to every session and 858 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.