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/govcon-pursuit-brain --skill qualifying-opportunitiesgit clone --depth 1 https://github.com/danielkinneyspears/govcon-pursuit-brainWrote 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/govcon-pursuit-brain/qualifying-opportunities)<a href="https://agentmods.dev/skills/danielkinneyspears/govcon-pursuit-brain/qualifying-opportunities"><img src="https://agentmods.dev/badge/skills/danielkinneyspears/govcon-pursuit-brain/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/govcon-pursuit-brain/qualifying-opportunities"><img src="https://agentmods.dev/badge/skills/danielkinneyspears/govcon-pursuit-brain/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.00115 | $0.02459 |
| Opus 5 | $0.00057 | $0.01229 |
| Sonnet 5 | $0.00023 | $0.00492 |
| Haiku 4.5 | $0.00012 | $0.00246 |
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 11d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Qualifying Opportunities
Decide whether to pursue or bid a US Federal opportunity — and, because this is usually the first skill to touch a pursuit, bootstrap the pursuit wiki it will live in. The expensive mistake in federal BD is spending bid-and-proposal money on bids that were never winnable; this skill makes that decision deliberately, on evidence, and records it as the first entities in the pursuit's knowledge graph.
When to use this skill
Use this skill at any bid/no-bid gate — an early pursuit decision, a preliminary bid decision, or post-RFP bid validation. It both renders the decision and, on first run, creates the pursuit wiki that every later skill builds on.
It does not build the win plan — that is planning-capture and
developing-win-strategy. It decides whether there should be a win plan at all.
Architecture
This skill is wiki-native. Read docs/architecture.md and the conventions before running it. The skill reads sources and the domain wiki, maintains pursuit entity pages, and renders views — it never writes a flat artifact as a source of truth.
Relevant domain-wiki pages: [[uniform-contract-format]], [[section-m]],
[[far-part-15-source-selection]], [[best-value-tradeoff]], [[lpta]].
Inputs
Required: the opportunity — a described lead, or a solicitation document
placed in pursuits/<id>/sources/.
Existing pursuit wiki, if this is not the first run: read pursuit.md and
the existing customer/, competitors/, and decisions/ entities; do not
re-create them.
Private company context (recommended). If pursuit.md carries a
company_context_path: field, read the relevant company-context pages
before intake — customers/<this-agency>/, past-performance/,
key-personnel/, pricing-guidance/, compliance-posture/,
debrief-lessons/, approved-proof-points/. Treat them as authoritative
sources for the questions they answer. See
../../docs/customize-for-your-company.md.
Without company-context, the skill still runs from intake — just with less
leverage.
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.
- 11d ago First seen · 198 lines · 115 tokens per session scan A 3d51f97930ef
qualifying-opportunities is a skill published in the GitHub repository danielkinneyspears/govcon-pursuit-brain (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 115 tokens to every session and 2,459 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
auditing-commitments
Audits a US Federal proposal draft for the obligations it creates, and flags promises stronger than the solicitation requires. Use when the user needs a commitment audit, a promise review, an obligation review, a check for overcommitting, a review of "we will" and "shall" language, a check that the draft does not…
analyzing-competitors
Produces a Black Hat competitive assessment for a US Federal opportunity. Use when the user needs competitive analysis, a Black Hat review or session, competitor profiling, an incumbent assessment, or wants to understand the competitive field for a federal bid. Identifies likely competitors, models each one's probable…
analyzing-debriefs
Prepares for and analyzes a US Federal procurement debrief. Use when the user needs to request a debrief, prepare debrief questions, analyze a government debrief, conduct win/loss analysis, or capture lessons learned from a federal bid. Structures the debrief request, interprets what the government said about the…
checking-submission-compliance
Runs the final production and submission-compliance check on a US Federal proposal before submission. Use when the user needs a submission compliance check, a final compliance review, a production check, a page-count or format check, a forms and certifications check, or a pre-submission checklist for a federal bid.…
developing-solution-approach
Designs the proposal-ready solution for a US Federal bid. Use when the user needs a solution approach, a technical solution design, solutioning, a solutioning workshop, a staffing or management model, a transition or risk or quality approach, or needs to turn requirements, win themes, and constraints into a designed…
developing-teaming-strategy
Develops the teaming strategy for a US Federal pursuit. Use when the user needs a teaming strategy, a partner gap analysis, teammate selection or scoring, workshare planning, teaming agreements or letters of intent, subcontractor data calls, small-business participation or subcontracting-plan input, or teaming OCI…