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/mbruhler/claude-orchestration/using-templatesnpx skills add mbruhler/claude-orchestration --skill using-templatesgit clone --depth 1 https://github.com/mbruhler/claude-orchestrationWrote 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/mbruhler/claude-orchestration/using-templates)<a href="https://agentmods.dev/skills/mbruhler/claude-orchestration/using-templates"><img src="https://agentmods.dev/badge/skills/mbruhler/claude-orchestration/using-templates.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.00034 | $0.01275 |
| Opus 5 | $0.00017 | $0.00638 |
| Sonnet 5 | $0.00007 | $0.00255 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade B, and why
using-templates scanned grade B with 1 finding 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/workflows/my-template.flow How it starts
The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Workflow Templates
I help you use and customize workflow templates for common automation scenarios.
When I Activate
I activate when you:
- Ask about available templates
- Want to use a workflow template
- Need to customize a template
- Ask "what templates exist?"
- Say "use the X template"
Template Locations
Templates are searched in the following locations (in order of priority):
- Project root:
./workflows/*.flow- Project-specific templates - Claude root:
~/.claude/workflows/*.flow- User's global templates - Plugin examples:
~/.claude/plugins/repos/orchestration/examples/*.flow- Built-in examples
Project-local templates take precedence over global templates.
Built-in Example Templates
Located in examples/ directory:
- tdd-implementation.flow - Test-Driven Development
- debug-and-fix.flow - Bug investigation and fixing
- polish-news-aggregation.flow - News data aggregation
- plugin-testing.flow - Plugin testing workflow
- i18n-fix-hardcoded-strings.flow - Internationalization
- ui-component-refinement.flow - UI component improvement
- agent-system-demo.flow - Agent system demonstration
Using Templates
1. List Templates
# List project templates
ls ./workflows/*.flow 2>/dev/null
# List user's global templates
ls ~/.claude/workflows/*.flow 2>/dev/null
# List built-in examples
ls ~/.claude/plugins/repos/orchestration/examples/*.flow
2. View Template
# View from any location
cat ./workflows/my-template.flow
cat ~/.claude/workflows/my-template.flow
cat ~/.claude/plugins/repos/orchestration/examples/tdd-implementation.flow
3. Execute Template
Use /orchestration:template command (searches all locations automatically):
/orchestration:template tdd-implementation
Or reference directly with path:
Use ./workflows/my-workflow.flow
Use ~/.claude/workflows/my-workflow.flow
Use examples/tdd-implementation.flow
Customizing Templates
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.
- 6d ago First seen · 245 lines · 34 tokens per session scan B 3aba2aac2582
using-templates is a skill published in the GitHub repository mbruhler/claude-orchestration (219 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 1,275 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…