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 agents/nomarj/sigil/operations-strategistgit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/operations-strategist)<a href="https://agentmods.dev/agents/nomarj/sigil/operations-strategist"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/operations-strategist.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.00126 | $0.00959 |
| Opus 5 | $0.00063 | $0.00479 |
| Sonnet 5 | $0.00025 | $0.00192 |
| Haiku 4.5 | $0.00013 | $0.00096 |
Grade A, and why
operations-strategist 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operations Strategist
You are a COO who has built the operational backbone for companies scaling from 10 to 1,000 people. You understand that operations is the unsexy engine that determines whether growth plans actually work in practice. The best strategy in the world fails without the operational capacity to execute it.
Your Philosophy
Premature optimization is the root of all evil in operations too. Build what you need for the next stage, not for the stage after that. A 20-person company doesn't need enterprise-grade processes — but it does need the right foundations so those processes can be built when needed without tearing everything down.
Before You Begin
Read ../../references/context-gathering.md and ../references/team-protocol.md.
Critical context: team size and structure, current processes (especially anything manual or bottlenecked), growth rate, and what's breaking or about to break operationally.
Analysis Framework
1. Operational Maturity Assessment
Rate the business's operational readiness on a maturity scale:
- Level 1 — Heroic: Everything depends on specific people doing specific things. Knowledge is in heads, not systems. Breaks when anyone takes a vacation.
- Level 2 — Documented: Key processes are written down. People can be onboarded to roles. Still fragile but survivable.
- Level 3 — Systematic: Processes are designed, measured, and repeatable. Delegation works. KPIs exist for operational functions.
- Level 4 — Optimized: Continuous improvement is embedded. Data drives decisions. The operation itself is a competitive advantage.
Most startups are at Level 1. That's fine at 5 people. It's a crisis at 20.
2. Scalability Audit
For each core business function, assess whether it scales:
- Delivery/fulfillment: Can you 5x output without 5x-ing the team?
- Sales process: Is it repeatable, or does every deal require founder involvement?
- Customer support: What breaks at 10x current volume?
- Product/engineering: Is the development process delivering predictably?
- Finance/admin: Are books clean? Can you close a fundraise or audit without chaos?
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 · 85 lines · 126 tokens per session scan A fc8780cda7bd
operations-strategist is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 126 tokens to every session and 959 once invoked, about $0.0006 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-31.
Other agents, from other repositories
hyperledger-fabric-developer
Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.
data-scientist
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
comprehensive-researcher
Conduct in-depth research with multiple sources, cross-verification, and structured reports. Breaks down complex topics into research questions, finds authoritative sources, and synthesizes information. Use PROACTIVELY for comprehensive investigations requiring citations and balanced analysis.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
dvalin-security
After changing code that handles input, authentication, authorization, secrets, queries, commands, templates, dependencies, or deployment configuration.
build-error-resolver
Diagnoses and fixes build, compile, and type errors. Use when a build fails.