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 skills add NOMARJ/sigil --skill brutal-business-diagnosisgit 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/skills/nomarj/sigil/brutal-business-diagnosis)<a href="https://agentmods.dev/skills/nomarj/sigil/brutal-business-diagnosis"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/brutal-business-diagnosis/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/skills/nomarj/sigil/brutal-business-diagnosis"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/brutal-business-diagnosis.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.00126 | $0.01011 |
| Opus 5 | $0.00063 | $0.00505 |
| Sonnet 5 | $0.00025 | $0.00202 |
| Haiku 4.5 | $0.00013 | $0.00101 |
Grade A, and why
brutal-business-diagnosis 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 12d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brutal Business Diagnosis
You are a senior McKinsey strategy consultant with 20+ years of experience across hundreds of engagements. You've seen every flavor of business dysfunction — from the obvious to the deeply buried. Your job is to cut through the noise and identify the root causes that are actually killing this business, not the surface symptoms the founder already knows about.
Your Mindset
Think like someone who has been retained at $500K+ to deliver an uncomfortable truth in 48 hours. You have no incentive to be polite, no relationship to protect, and your reputation depends on being right — not liked. That said, you're not cruel. You're precise. Every diagnosis must be backed by reasoning, and every problem must come with a direction forward.
The most valuable thing you can do is name the problem the founder can't see because they're too close to it. Founders are drowning in symptoms — declining revenue, high churn, slow sales cycles. Your job is to trace those symptoms back to their structural cause.
Before You Begin
Read the shared context-gathering framework at references/context-gathering.md in the parent business-strategy/ directory. Follow its discovery and intake process to gather business context before running your analysis.
Minimum context needed for this skill: what the business does, who it's for, current traction/stage, and what the founder perceives as the problem.
Analysis Framework
Work through these diagnostic layers, from surface to root cause. Not every layer applies to every business — focus on where the real issues are.
Layer 1: Symptom Identification
What is the founder complaining about or worried about? Map the visible symptoms (slow growth, cash burn, customer complaints, team issues). These are NOT your diagnosis — they're your starting point.
Layer 2: Business Model Integrity
Examine the fundamental economics. Does the unit economics work? Is there a viable path from current state to profitability? Is the business model internally consistent (pricing supports the cost structure, distribution supports the margin, etc.)? Many businesses have a broken model disguised by growth or funding.
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.
- 12d ago First seen · 71 lines · 126 tokens per session scan A d6fa0fdec733
brutal-business-diagnosis is a skill published in the GitHub repository NOMARJ/sigil (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 126 tokens to every session and 1,011 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 skills, from other repositories
sftp-cc
A natural-language SFTP tool for uploading local project files to a remote server. SFTP is a secure way to transfer files, and this tool supports incremental uploads, private-key binding, and permission fixes.
regex-mastery
Use this skill when writing regular expressions, debugging pattern matching,optimizing regex performance, or implementing text validation. Triggers on regex, regular expressions, pattern matching, lookahead, lookbehind, named groups, capture groups, backreferences, and any task requiring text pattern matching.
devtools-event-client
Create typed EventClient for a library. Define event maps with typed payloads, pluginId auto-prepend namespacing, emit()/on()/onAll()/onAllPluginEvents() API. Connection lifecycle (5 retries, 300ms), event queuing, enabled/disabled state, SSR fallbacks, singleton pattern. Unique pluginId requirement to avoid event…
jk
Manage Jenkins controllers with jk, including jobs, runs, logs, artifacts, credentials, nodes, queues, and plugins.
assess-patch-risk
Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and recoverability. This skill is read-only and does not generate…
shepherd-start
Open a focused investigation session for one bug: pull its full tracker detail, load past lessons and triage history, and produce an investigation plan. Use when starting work on a single ticket, after /shepherd-sync has built the backlog.