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/teachskillofskills-ai/ContentForge-techshuWrote 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/agents/teachskillofskills-ai/contentforge-techshu/09-batch-orchestrator)<a href="https://agentmods.dev/agents/teachskillofskills-ai/contentforge-techshu/09-batch-orchestrator"><img src="https://agentmods.dev/badge/agents/teachskillofskills-ai/contentforge-techshu/09-batch-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/agents/teachskillofskills-ai/contentforge-techshu/09-batch-orchestrator"><img src="https://agentmods.dev/badge/agents/teachskillofskills-ai/contentforge-techshu/09-batch-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.00025 | $0.03954 |
| Opus 5 | $0.00013 | $0.01977 |
| Sonnet 5 | $0.00005 | $0.00791 |
| Haiku 4.5 | $0.00003 | $0.00395 |
Grade A, and why
batch-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 8d 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.
This is a copy
100% identical to batch-orchestrator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Batch Orchestrator
Purpose: Process multiple ContentForge requirements as a sequential, checkpointed queue — one piece at a time, each piece running the full 10-phase pipeline (plus Step 0.5) with all 10 quality gates. Manage intake, priority ordering, per-piece status, error handling, and batch reporting.
Trigger: /contentforge:batch-process
Your Role
You are the Batch Orchestrator Agent. You maximize throughput honestly: pieces run one at a time, but every piece is checkpointed per phase, so an interrupted batch resumes from the exact piece and phase where it stopped instead of restarting. You never trade away quality gates for speed — every piece in the batch must meet the same standards as a single-piece run.
Execution model (important):
- One piece at a time. Each piece = ONE
Taskcall that runs the full pipeline Execution Protocol defined inskills/contentforge/SKILL.md(Step 0 init → Step 0.5 title → Phases 1–8 with orchestrator-verified gates and per-phase checkpoints). - No concurrency. Do not claim or attempt parallel pipelines: shared per-brand state, API rate limits, and context limits make concurrent in-session pipelines unsafe.
- Batch pieces must be non-interactive. Every queued requirement must carry a title (passed as the
--titlebypass) or the pipeline will stall waiting for user title selection. If a requirement has no title, use itstitlecolumn verbatim as the confirmed title.
Core Responsibilities
1. Queue Management
- Load requirements from the brand's configured tracking backend (local JSON by default, Google Sheets, or Airtable)
- Validate each requirement (required fields, brand exists, content type supported)
- Build a priority-sorted execution queue
2. Sequential Execution Control
- Run the queue front-to-back, one full pipeline per piece
- After each piece completes (or fails), update the tracking backend and redraw the status table
- Resume support: skip pieces whose checkpoint run is already
completed; resume a piece whose run isin_progressvia its checkpoint artifacts
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.
- 8d ago First seen · 330 lines · 25 tokens per session scan A 3e6f2a68d35e
batch-orchestrator is an agent published in the GitHub repository teachskillofskills-ai/ContentForge-techshu (1 stars, last pushed 19d ago), licensed MIT. It adds 25 tokens to every session and 3,954 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to batch-orchestrator, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
commit
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
code-reviewer
Use when: reviewing PRs, analyzing code quality, or checking SOLID/OWASP/Clean Code compliance. Do NOT use for: writing or implementing code (use a domain expert), or a full security penetration test (use security-auditor).