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 qualifying-opportunitiesgit 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/qualifying-opportunities)<a href="https://agentmods.dev/skills/danielkinneyspears/federal-proposal-skills/qualifying-opportunities"><img src="https://agentmods.dev/badge/skills/danielkinneyspears/federal-proposal-skills/qualifying-opportunities/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/qualifying-opportunities"><img src="https://agentmods.dev/badge/skills/danielkinneyspears/federal-proposal-skills/qualifying-opportunities.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.00104 | $0.01923 |
| Opus 5.5 | $0.00042 | $0.00769 |
| Sonnet 5.5 | $0.00021 | $0.00385 |
| Haiku 4.5 | $0.00010 | $0.00192 |
Grade A, and why
qualifying-opportunities 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 2mo 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Qualifying Opportunities
Run a disciplined bid/no-bid gate review on a US Federal opportunity and produce a defensible recommendation. The expensive mistake in federal BD is not losing a bid — it is spending bid-and-proposal money on bids that were never winnable. This skill exists to make that decision deliberately, on evidence, against a consistent standard.
When to use this skill
Use this skill when a user needs to decide whether to pursue or bid a federal opportunity, at any gate:
- A new lead or sources-sought notice has appeared and the question is whether to invest capture resources.
- A draft RFP or RFP has released and the question is whether to bid.
- An opportunity already in the pipeline is reaching a gate review.
Do not use this skill to build the win plan — that is planning-capture and
developing-win-strategy. This skill decides whether there should be a win plan
at all. If the decision is already made and the user wants positioning work,
route to those skills instead.
Inputs
Preferred upstream artifacts (from the pursuit workspace, if present):
03-competitive-assessment.md: sharpens the competitive-position scoring.04-price-to-win.md: sharpens the financial and competitiveness scoring.
Without them, the skill still runs: it scores competitive position from what the user knows and records the lower confidence. A bid/no-bid decision is often made before deep competitive and price analysis exists; that is expected.
Read ../../shared/glossary.md, ../../shared/proposal-lifecycle.md, and
../../shared/pursuit-workspace.md if you have not already this session.
Intake
Before scoring anything, establish the facts. Ask the user these questions as a
numbered list. Skip any already answered by a solicitation document or an
existing 00-opportunity-profile.md in the workspace. Do not guess answers —
unknown is a valid and important answer that lowers confidence and often the
score.
- The opportunity. What is it — agency/office, scope of work, contract type, estimated value, period of performance, set-aside status, and solicitation/notice number? Is there a document (RFI, sources-sought, draft RFP, RFP) available to read?
- The gate. Which decision is this — an early pursuit decision (invest capture resources?) or a bid decision/bid validation (commit to proposing?)? How long until the proposal would be due?
- Customer relationship. What is the prior relationship with this customer and office? Has the team shaped this requirement, engaged the customer, or responded to an RFI/draft RFP? Is there an incumbent, and is it the user's organization?
- Capability and past performance. Can the organization actually perform this work? Is there recent, relevant, similarly sized past performance? Are required clearances, certifications, facility approvals, or NAICS size standards met?
- Competition and price. Who is likely to bid, and what is the realistic read on competitiveness? Is funding confirmed? Is there a known or estimated budget?
- Strategic fit and constraints. Does this fit the organization's strategy and growth direction? Are there blockers — OCI, a teaming dependency, a missing vehicle, capacity limits, or unacceptable contract terms?
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.
- 2mo ago First seen · 146 lines · 104 tokens per session scan A 999f32cb9f7c
qualifying-opportunities is a skill published in the GitHub repository danielkinneyspears/federal-proposal-skills (8 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 104 tokens to every session and 1,923 once invoked, about $0.0004 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.
qualifying-opportunities compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| qualifying-opportunitiesdanielkinneyspears/federal-proposal-skills | Skill | 8 | 3mo ago | Apache-2.0 | A | 104 | Claude Code |
| qualifying-opportunitiesdanielkinneyspears/govcon-pursuit-brain | Skill | 7 | 1mo ago | Apache-2.0 | A | 115 | Claude Code |
| analyzing-competitorsdanielkinneyspears/govcon-pursuit-brain | Skill | 7 | 1mo ago | Apache-2.0 | A | 108 | Claude Code |
| market-research-workflow1102tools-dev/federal-contracting-skills | Skill | 25 | 2mo ago | MIT | A | 159 | Codex |
| govcon-growth-workflow1102tools-dev/federal-contracting-skills | Skill | 25 | 2mo ago | MIT | A | 115 | Codex |
| igce-builder-cr1102tools-dev/federal-contracting-skills | Skill | 25 | 2mo ago | MIT | A | 161 | Codex |
| igce-builder-ffp1102tools-dev/federal-contracting-skills | Skill | 25 | 2mo ago | MIT | A | 188 | Codex |