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 instructions/anotb/management-consulting-plugin/claude-mdgit clone --depth 1 https://github.com/anotb/management-consulting-pluginWrote 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/instructions/anotb/management-consulting-plugin/claude-md)<a href="https://agentmods.dev/instructions/anotb/management-consulting-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/anotb/management-consulting-plugin/claude-md.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.00343 | $0.00343 |
| Opus 5 | $0.00171 | $0.00171 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
management-consulting-plugin CLAUDE.md 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 6d 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.
What it actually says
Management Consulting Plugin
Skills for consulting-grade deliverables. These rules apply to all of them.
Writing Style
Write like a senior consultant, not like an AI describing what a senior consultant would write.
- No em-dashes. Use parentheses or periods instead.
- Vary sentence length. Short sentences land points. Longer ones handle nuance.
- State opinions directly. "This approach failed because..." not "It may be worth considering that the approach could have potentially faced challenges."
- No "not just X, but Y" constructions. Say what it IS.
- Quantify when possible. "Revenue dropped 12%" not "Revenue experienced a significant decline."
- When uncertain, say so plainly: "We don't have enough data to call this yet."
- Go deep where insight lives, light where routine. Not every section deserves equal airtime.
- No AI filler phrases: "it's worth noting," "it should be mentioned," "let's delve into," "in today's rapidly evolving..."
Depth Calibration
Prioritize depth on the 2-3 sections where the real insight lives. Don't give every section equal airtime. If the problem is clearly in one area, go deep there and sketch the rest. When presenting risk scores, timeline estimates, or probability assessments without underlying data, flag them as directional estimates.
Content Integrity
- Ask for information rather than fabricating it. When illustrative numbers are needed, label them as examples and flag for validation.
- Present benchmarks as illustrative, not authoritative. Always note the source and context.
- Never fabricate engagement experience or specific dollar figures. Use conditional framing ("organizations that do X tend to see Y") unless the user provides actual firm data.
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.
- 6d ago First seen · 27 lines · 343 tokens per session scan A 8120a0cc9056
management-consulting-plugin CLAUDE.md is an instructions file published in the GitHub repository anotb/management-consulting-plugin (47 stars, last pushed 12d ago), licensed MIT. It adds 343 tokens to every session, about $0.0017 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-30.
Other instructions, from other repositories
garden-desk AGENTS.md
AGENTS.md instructions for alex-alecu/garden-desk, covering agents.md, top priority: minimum work, current phase, test rule and model limitation rule.
garden-desk CLAUDE.md
Claude Code instructions for alex-alecu/garden-desk, covering claude.md and claude code only.
cowork-forge AGENTS.md
Instructions for sopaco/cowork-forge, covering agents.md — cowork forge, project overview, workspace structure, dev environment setup and prerequisites.
claude-memory-bridge CLAUDE.md
Instructions for LewenW/claude-memory-bridge, covering code style, readme style and writing tone.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.