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 skills/anotb/management-consulting-plugin/proposal-developmentnpx skills add anotb/management-consulting-plugin --skill proposal-developmentgit 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/skills/anotb/management-consulting-plugin/proposal-development)<a href="https://agentmods.dev/skills/anotb/management-consulting-plugin/proposal-development"><img src="https://agentmods.dev/badge/skills/anotb/management-consulting-plugin/proposal-development.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.00112 | $0.04335 |
| Opus 5 | $0.00056 | $0.02167 |
| Sonnet 5 | $0.00022 | $0.00867 |
| Haiku 4.5 | $0.00011 | $0.00434 |
Grade A, and why
proposal-development 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 4d 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proposal Development
Run the full business development lifecycle for a consulting pursuit: assess the opportunity, articulate value, write the proposal, draft the SOW, build the pitch deck. This covers everything up to award. For deliverables produced during an engagement (steering committee decks, final reports), see client-deliverables.
A full pursuit flows through the five stages in order. Most users enter mid-stream. Identify which stage the request lands in, confirm the inputs that stage needs, then execute. Do not walk someone through opportunity scoring when they hand you a signed engagement and ask for a SOW.
One rule threads through all five stages: work from real inputs. Ask for the client's actual words, the actual RFP text, the firm's actual case results. When you need an illustrative number to show structure, label it as an example and flag it for validation. Never invent engagement experience, competitor intelligence, or dollar figures. Frame outcome claims conditionally ("organizations that consolidate vendors this way tend to cut spend 8-15%") unless the user supplies real firm data with a source.
Stage 1: Opportunity Assessment
Decide whether and how to respond before anyone burns hours on a draft. This stage is where pursuits are won or wasted, so give it real attention.
1a. Parse the opportunity
Read the source material (RFP, inbound request, conversation notes, or opportunity brief) and pull out:
- Client organization: who they are, their situation, why they are buying now
- Problem statement: the challenge they are actually trying to solve, which is often not the one the RFP names
- Scope: what they are asking for
- Deliverables: what must be produced
- Timeline: key dates, including the submission deadline
- Budget: if disclosed. If not, flag it as a risk and plan to size it yourself
- Evaluation criteria: how responses get scored
- Submission requirements: format, page limits, mandatory sections
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 384 lines · 112 tokens per session scan A cec057bfaa34
proposal-development is a skill published in the GitHub repository anotb/management-consulting-plugin (47 stars, last pushed 10d ago), licensed MIT. It adds 112 tokens to every session and 4,335 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-30.
Other skills, from other repositories
html-ppt-zhangzara-mat
A margin-recovery diagnosis for a regional grocery chain — the governing thought, the driver tree, the priorities, and the roadmap. Built as a decision-grade consulting deck for client sponsor, steering committee.
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…
autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when…
pre-landing-review
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when explicitly asked for the specialized pre-landing workflow. Product /review requests are handled by BitFun's unified Review mechanism instead.…
miniapp-dev
Develops, maintains, and generates BitFun MiniApps (Zero-Dialect Runtime). Use when (1) working on miniapp framework code under src/crates/assembly/core/src/miniapp/ or src/web-ui/src/app/scenes/miniapps/; or (2) generating / creating / designing a NEW MiniApp for the user — including any request like "做一个小应用 / 生成…