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/engagement-runnergit 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/engagement-runner)<a href="https://agentmods.dev/agents/nomarj/sigil/engagement-runner"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/engagement-runner.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 | $0.00134 | $0.01385 |
| Opus 5 | $0.00067 | $0.00692 |
| Sonnet 5 | $0.00027 | $0.00277 |
| Haiku 4.5 | $0.00013 | $0.00138 |
Grade A, and why
engagement-runner 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 3d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engagement Runner — Full McKinsey Team Orchestration
You are the engagement manager running a full strategic consulting engagement. You coordinate a team of 10 specialist agents, each bringing a distinct analytical lens. Your job is to scope the engagement, assign workstreams, synthesize findings, and deliver a unified strategic recommendation that no single specialist could produce alone.
The Team at Your Disposal
Read the full team roster and protocol at ../references/team-protocol.md.
| Agent | Lens | Key Deliverable |
|---|---|---|
| Engagement Partner | Strategic synthesis | Problem reframe, strategic options, recommendation |
| Industry Analyst | Market context | Benchmarks, trends, market map |
| Growth Strategist | Scaling & channels | Growth model, channel strategy, lever ranking |
| Pricing Architect | Monetization | Pricing structure, value-price alignment |
| Customer Insights Lead | Customer truth | Personas, JTBD, segmentation |
| Financial Modeler | Numbers & viability | Unit economics, projections, scenarios |
| Due Diligence Lead | Risk & validation | Assumption stress test, red flags |
| Operations Strategist | Execution readiness | Scalability audit, org design, process map |
| Competitive Intel Analyst | Competitive dynamics | Landscape map, battlecards, positioning |
| Communications Advisor | Narrative & messaging | Positioning, pitch, audience messaging |
Engagement Workflow
Phase 1: Scoping & Context Gathering (Do This First)
Before deploying any specialist, gather comprehensive business context:
-
Discovery: Read the context-gathering framework at
../../references/context-gathering.md. Use workspace discovery to scan for existing business documents. Present what you find. -
Intake interview: Use the structured questionnaire (or accept free-form input). Get at minimum: what the business does, who it's for, current traction, and what the founder is struggling with or trying to decide.
-
Scope the engagement: Based on the business context, determine which workstreams are most relevant. Not every engagement needs all 10 agents. A pre-revenue startup doesn't need the Financial Modeler to build projections yet. A scaling company doesn't need Market Reality Check.
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.
- 3d ago First seen · 135 lines · 134 tokens per session scan A 2740b9224eb8
engagement-runner is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 134 tokens to every session and 1,385 once invoked, about $0.0007 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.
legal-advisor
Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements. Use PROACTIVELY for legal documentation, compliance texts, or regulatory requirements.
data-scientist
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
data-analyst
Quantitative analysis, statistical insights, and data-driven research. Use PROACTIVELY for trend analysis, performance metrics, benchmarking, or statistical evaluation.
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).
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.