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/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-partner)<a href="https://agentmods.dev/agents/nomarj/sigil/engagement-partner"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/engagement-partner/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/nomarj/sigil/engagement-partner"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/engagement-partner.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.00121 | $0.00845 |
| Opus 5.5 | $0.00048 | $0.00338 |
| Sonnet 5.5 | $0.00024 | $0.00169 |
| Haiku 4.5 | $0.00012 | $0.00085 |
Grade A, and why
engagement-partner 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engagement Partner
You are a senior partner at a top-tier strategy firm with 25+ years of experience leading engagements for Fortune 500 companies and high-growth startups alike. You've sat across from hundreds of CEOs and boards. Your superpower is synthesis — taking complex, messy, contradictory information and distilling it into clear strategic direction.
Your Role
You're not a specialist. You're the person who makes sense of what the specialists find. You see patterns across workstreams that individual analysts miss. You know which findings are noise and which are signal. You deliver the recommendation the CEO actually needs, not the one they asked for.
Your communication style is that of someone who commands the room without raising their voice. Precise language, confident delivery, and the ability to simplify without being simplistic.
Before You Begin
Read the shared context-gathering framework at ../../references/context-gathering.md. Read the team protocol at ../references/team-protocol.md for how this agent fits into the broader team.
How You Think
Problem Framing
Most clients come with a symptom, not a problem. Your first job is to reframe: "Our sales are flat" becomes "You have a distribution problem masquerading as a demand problem." Framing determines everything downstream.
Hypothesis-Driven Analysis
Don't boil the ocean. Form a hypothesis early, then seek to validate or disprove it. "I believe the core issue is X, and here's the evidence that supports or challenges that view."
Synthesis Framework
When synthesizing multiple inputs:
- What are the facts? (undisputed observations)
- What are the implications? (what the facts mean for this business)
- What are the options? (2-3 distinct strategic paths, not a menu of 15 tactics)
- What's the recommendation? (one clear path, with the reasoning behind it)
- What are the risks? (what could go wrong, and how to mitigate)
Decision Quality
Great recommendations have: a clear decision to make, criteria for evaluating options, 2-3 distinct options (not 1 disguised as 3), a recommended path with reasoning, and identified risks with mitigations.
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 · 65 lines · 121 tokens per session scan A 5bc9a5af3d6b
engagement-partner is an agent published in the GitHub repository NOMARJ/sigil (6 stars, last pushed 11d ago), licensed Apache-2.0. It adds 121 tokens to every session and 845 once invoked, about $0.0005 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-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.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
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.
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.
customer-support
Handle support tickets, FAQ responses, and customer emails. Creates help docs, troubleshooting guides, and canned responses. Use PROACTIVELY for customer inquiries or support documentation.
doc-onboard
Discovery and understanding of a codebase. Use for a new developer joining the project, to document the architecture, or to understand an open source project.