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/maigentic/stratartsWrote 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/commands/maigentic/stratarts/operational-playbook-creator)<a href="https://agentmods.dev/commands/maigentic/stratarts/operational-playbook-creator"><img src="https://agentmods.dev/badge/commands/maigentic/stratarts/operational-playbook-creator/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/commands/maigentic/stratarts/operational-playbook-creator"><img src="https://agentmods.dev/badge/commands/maigentic/stratarts/operational-playbook-creator.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.00046 | $0.08146 |
| Opus 5.5 | $0.00018 | $0.03258 |
| Sonnet 5.5 | $0.00009 | $0.01629 |
| Haiku 4.5 | $0.00005 | $0.00815 |
Grade A, and why
operational-playbook-creator 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.
How it starts
The opening of the file, as written. The whole thing — 865 lines — stays where its author put it; the contents beside it link to each section on GitHub.
operational-playbook-creator
Mission: Create a comprehensive operational playbook documenting how your company runs—organizational structure, processes, meeting rhythms, communication protocols, culture, goal-setting, decision-making, tools, and onboarding. Build the operating system that scales your team from 10 to 100 to 1,000+ employees.
STEP 0: Pre-Generation Verification
MANDATORY: Complete this checklist BEFORE generating output.
Information Requirements
- Company name and stage confirmed
- Current headcount and organizational structure documented
- Core values (3-5) defined with behavioral descriptions
- Mission and vision statements available
- Meeting rhythm preferences understood (cadence, duration, participants)
- Communication tool preferences identified (Slack vs Teams, etc.)
- OKR/goal-setting framework preference confirmed
- Tool stack inventory available
- Onboarding timeline expectations set
Output Format Verification
- HTML template located at
html-templates/operational-playbook-creator.html - Score banner metrics: Headcount, Departments, Core Processes, Meetings, Tools, Y1 Target
- All 10 sections have content ready:
- Company Foundation (mission, vision, 3-5 values)
- Organizational Structure (org chart + headcount growth chart)
- Core Processes (4 department processes minimum)
- Meeting Rhythms (daily, weekly, bi-weekly, monthly, quarterly)
- Communication Protocols (channels + SLA cards)
- OKRs & Goals (3 objectives with 2-3 KRs each)
- Tools & Systems (10-15 tools with categories)
- Onboarding Playbook (5-stage timeline)
- Company Culture & Rituals (6 rituals across cadences)
- Next Steps (6 prioritized action items)
- Chart.js data prepared for headcount growth chart
- All placeholder markers identified for replacement
Quality Gates
- Processes are specific, not generic (includes timing, owners, SLAs)
- Values include behavioral definitions (what it looks like in practice)
- Meeting rhythms are realistic (not excessive for company size)
- Onboarding covers Pre-Day 1 through Day 30
- OKRs follow proper format (qualitative O, quantitative KRs)
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 First seen · 865 lines · 46 tokens per session scan A 394232dfbdf0
operational-playbook-creator is a command published in the GitHub repository maigentic/stratarts (45 stars, last pushed 8mo ago), licensed MIT. It adds 46 tokens to every session and 8,146 once invoked, about $0.0002 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 commands, from other repositories
poc
Before building on an unproven idea, get a timeboxed yes/no answer — start a hypothesis-driven POC that skips 80% of the production pipeline and forces ship/pivot/kill at expiry, then promote a shipped POC through the audits it skipped.
spec
Know the problem but not yet the product, the requirements or the design? Run it — you get, stage by stage, a discovery plan (/spec discover), a PRD (/spec prd) and a build spec: requirements.md + design.md + tasks.md (/spec or /spec build). Run before writing any code.
ownership
When you need to know who owns a path and who answers for it — the service ownership matrix (team, lead, on-call, SLA) auto-detected from git with CODEOWNERS generated, plus on-call rotations, shift handoffs and escalation paths.
rfc
RFC process for cross-team decisions. Create, track, and close RFCs. Accepted RFCs auto-create ADRs.
exception
Signed gate-exception registry — replace ad-hoc --admin / --no-verify bypasses with an auditable, signed, expiring record (who · why · gate · scope · expiry). Create / list / check exceptions.
issues
Create GitHub issues from research findings as atomic deliverables.