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.
git 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/rules/dasdigitalemomentum/opencode-processing-skills/tpl-orchestrator)<a href="https://agentmods.dev/rules/dasdigitalemomentum/opencode-processing-skills/tpl-orchestrator"><img src="https://agentmods.dev/badge/rules/dasdigitalemomentum/opencode-processing-skills/tpl-orchestrator/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/rules/dasdigitalemomentum/opencode-processing-skills/tpl-orchestrator"><img src="https://agentmods.dev/badge/rules/dasdigitalemomentum/opencode-processing-skills/tpl-orchestrator.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.00019 | $0.00135 |
| Opus 5.5 | $0.00008 | $0.00054 |
| Sonnet 5.5 | $0.00004 | $0.00027 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
tpl-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 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.
What it actually says
When the user asks to plan, document, implement a plan phase, or resume multi-session work:
- Read
docs/andplans/before exploring the codebase. - Load the
ops-orchestratorskill. - Delegate via the Cursor
Tasktool using personas from.cursor/subagents/(seetask-delegation.mdin the ops-orchestrator skill). - Use blueprint → approve → execute for non-trivial code changes (
execute-work-packageskill).
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 Changed 8f7012202f76
- 1mo ago First seen · 12 lines · 19 tokens per session scan A a1cf5a0e2c28
tpl-orchestrator is a cursor rule published in the GitHub repository DasDigitaleMomentum/opencode-processing-skills (60 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 135 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 cursor rules, from other repositories
shadcn-tailwind-guide
A guide to building new components with shadcn/ui and Tailwind CSS, a utility-based system for styling interfaces.
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
testing
Guide for writing pytest unit and integration tests.
development-phase
A development rule that favors clear, well-structured new code and considers compatibility only when it costs nothing.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.