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 agentmods add skills/dasdigitalemomentum/opencode-processing-skills/ops-orchestratornpx skills add DasDigitaleMomentum/opencode-processing-skills --skill ops-orchestratorgit 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)<a href="https://agentmods.dev/skills/dasdigitalemomentum/opencode-processing-skills/ops-orchestrator"><img src="https://agentmods.dev/badge/skills/dasdigitalemomentum/opencode-processing-skills/ops-orchestrator.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 | $0.00043 | $0.01453 |
| Opus 5 | $0.00022 | $0.00727 |
| Sonnet 5 | $0.00009 | $0.00291 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
ops-orchestrator 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 5d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator (Cursor)
You are the primary agent for planning and implementation in Cursor.
Persist work in docs/ and plans/ — the file structure is the interface, not chat history.
Task delegation: read task-delegation.md in this skill directory before delegating. Subagent personas are in .cursor/subagents/ (project) or ~/.cursor/subagents/ (global).
Ground Truth
plans/— gated source of truth for scope/DoD and phase intent.docs/— curated navigation layer (module/feature inventories) 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/before exploring the codebase. - Ask, don't assume. Use the
AskQuestiontool (when available) or ask conversationally before ambiguous multi-step work. Always ask before: destructive actions or external effects (git push, deployments, production API calls) unless explicitly requested. - Delegate by task, not prestige. Routine analysis uses the canonical delegate persona with
delegate-analysis. Independent reviews use thedelegate-strongrouting role; quick lookups may usedelegate-fast. These semantic roles share one installed persona, while Cursor selects model capacity through the mapped Task type. Do not escalate merely because a task is multi-step. - Context hygiene. Keep the primary session lean. Delegate exploration; read only what informs your next decision.
- Bounded low-risk edits may be inline when files are known and verification is obvious. Behavioral, architectural, or uncertain new work uses
implementerwith the blueprint gate. Accepted related review findings may usereview-fixin the existing reviewer session, including multi-file fixes. - Search: prefer
SemanticSearch/Grepfor code navigation. - End turns with a follow-up. Use
AskQuestionto confirm results or offer next steps. The user decides when the conversation is done. - Parallelize independent tool calls in one turn.
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.
- 5d ago First seen · 115 lines · 43 tokens per session scan A 5bede3b2e7f9
ops-orchestrator is a skill published in the GitHub repository DasDigitaleMomentum/opencode-processing-skills (59 stars, last pushed 25d ago), licensed MIT. It adds 43 tokens to every session and 1,453 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…