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 danielkinneyspears/federal-proposal-skills --skill developing-win-strategygit clone --depth 1 https://github.com/danielkinneyspears/federal-proposal-skillsWrote 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/danielkinneyspears/federal-proposal-skills/developing-win-strategy)<a href="https://agentmods.dev/skills/danielkinneyspears/federal-proposal-skills/developing-win-strategy"><img src="https://agentmods.dev/badge/skills/danielkinneyspears/federal-proposal-skills/developing-win-strategy/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/danielkinneyspears/federal-proposal-skills/developing-win-strategy"><img src="https://agentmods.dev/badge/skills/danielkinneyspears/federal-proposal-skills/developing-win-strategy.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.00095 | $0.01671 |
| Opus 5 | $0.00048 | $0.00835 |
| Sonnet 5 | $0.00019 | $0.00334 |
| Haiku 4.5 | $0.00010 | $0.00167 |
Grade A, and why
developing-win-strategy 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 9d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developing Win Strategy
Turn customer knowledge and competitive analysis into a win strategy: the validated discriminators, the substantiated win themes, the ghosting language, and the plan for the team's own exposures. This is the difference between a proposal that is merely compliant and one that is built to win. Compliance answers every requirement. A win strategy gives the evaluator a reason to pick this offer over the others.
When to use this skill
Use this skill late in capture, once customer hot buttons, the competitive
field, and the price posture are understood, to set the strategy the proposal
will execute. The win strategy is the bridge from capture to proposal
development: outlining-proposals, drafting-proposal-sections, and
writing-executive-summaries all consume it.
Re-run it when the RFP releases and Section M is known, to map themes to the actual evaluation factors and re-test discriminators against the real criteria.
Inputs
Preferred upstream artifacts:
02-capture-plan.md: customer hot buttons, biases, and the requirement read.03-competitive-assessment.md: competitors' likely themes, the ghosting opportunities, and the team's exposures.04-price-to-win.md: the price posture the strategy must be consistent with.- The solicitation, if released — Section M evaluation factors.
Without the upstream artifacts, the skill runs from intake, but a win
strategy built without a competitive assessment cannot validate the rarity
half of a discriminator. Flag that limitation clearly and recommend running
analyzing-competitors first.
Read ../../shared/glossary.md and ../../shared/pursuit-workspace.md if not
already read this session.
Intake
Ask these as a numbered list. Skip what upstream artifacts answer.
- Customer hot buttons. What does this customer care about most — the past
pain, the risks they fear, the mission pressures, the priorities? (See
references/customer-hot-buttons.mdfor how to surface and validate these.) - Candidate strengths. What does the team believe it does well for this requirement and customer — capabilities, past performance, people, approach, relationships?
- The competitive field. Who is competing, and what would each competitor claim as their discriminators? (This is what tests whether the team's strengths are actually rare.)
- The team's exposures. Where is the team weak, and what will competitors ghost about the team's likely offer?
- Evaluation factors. If the RFP is out, what are the Section M factors and their relative importance? If not, what is the best read of how the customer will evaluate?
- Price posture. What pricing posture is the bid taking (from the price-to-win analysis), and does the strategy need to defend a premium or win on price?
What ships with it
3 files 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.
- 9d ago First seen · 145 lines · 95 tokens per session scan A 0794398b48a5
developing-win-strategy is a skill published in the GitHub repository danielkinneyspears/federal-proposal-skills (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 95 tokens to every session and 1,671 once invoked, about $0.0005 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
analyzing-competitors
Produces a Black Hat competitive assessment for a US Federal opportunity as a wiki of competitor entities. Use when the user needs competitive analysis, a Black Hat review or session, competitor profiling, an incumbent assessment, or to understand the competitive field for a federal bid. Creates and enriches one…
qualifying-opportunities
Runs a structured bid/no-bid gate review for a US Federal opportunity and bootstraps the pursuit's knowledge wiki. Use when deciding whether to pursue or bid a federal solicitation, RFP, RFQ, RFI, sources-sought notice, or IDIQ task order — for a bid/no-bid decision, pursuit decision, gate review, opportunity…
igce-builder-ffp
Trigger for: FFP IGCE, firm-fixed-price estimate, FFP cost model, proposed FFP rate validation, wrap-rate analysis, Agency BPA rate comparison, price-reasonableness memo, or fair-and-reasonable analysis. Build auditable Firm-Fixed-Price federal estimates using BLS OEWS wages, layered fringe/overhead/G&A/profit, GSA…
market-research-workflow
Trigger for: federal acquisition market research; FAR Part 10 reports; refreshing an existing market research report; analyzing commerciality, competition, small-business availability, contract type, consolidation, prior awards, vendors, or market conditions; or preparing supported findings for a Pre-Award Agent. A…
acquisition-policy-workflow
Trigger for: explaining current FAR, DFARS, or agency-supplement text; determining documented acquisition-policy status for an agency and FAR part; comparing codified text, RFO model text, and agency deviations; tracing acquisition rulemaking; finding procurement comment periods; analyzing public comments; refreshing…
govcon-growth-workflow
Trigger for: finding federal opportunities; capture and bid screening; competitor or incumbent intelligence; recompete pipelines; teaming partner research; agency, customer, or market intelligence; federal labor-rate or pricing context; or refreshing prior GovCon research. Always begin with the local SAM.gov…