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-teaming-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-teaming-strategy)<a href="https://agentmods.dev/skills/danielkinneyspears/federal-proposal-skills/developing-teaming-strategy"><img src="https://agentmods.dev/badge/skills/danielkinneyspears/federal-proposal-skills/developing-teaming-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-teaming-strategy"><img src="https://agentmods.dev/badge/skills/danielkinneyspears/federal-proposal-skills/developing-teaming-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.00084 | $0.01504 |
| Opus 5 | $0.00042 | $0.00752 |
| Sonnet 5 | $0.00017 | $0.00301 |
| Haiku 4.5 | $0.00008 | $0.00150 |
Grade A, and why
developing-teaming-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 10d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developing Teaming Strategy
Build the team. Most federal pursuits cannot be won by the prime alone — there are capability gaps, past-performance gaps, socioeconomic requirements, or scope that a partner does better. Teaming is the workstream that turns "we need help" into a defined team with defined workshare, signed agreements, and the data the proposal needs. Done late or loosely, teaming becomes the thing that constrains the bid; done deliberately, it is a source of strength.
When to use this skill
Use this skill during the capture phase, once the opportunity is being pursued and the requirement is understood well enough to see where the prime needs help. Re-run it as the requirement firms up through the draft RFP and RFP.
It is related to but distinct from planning-capture (which tracks teaming
actions at a summary level) and developing-solution-approach (which designs
what the team does). This skill decides who is on the team and on what
terms.
Inputs
Preferred upstream artifacts:
00-opportunity-profile.md: scope, contract type, set-aside, vehicle.02-capture-plan.md: the capability and past-performance gaps already noted.01-bid-decision.md: gaps the bid/no-bid identified, including any that were conditional-bid conditions.03-competitive-assessment.md: what the team must be strong enough to beat.
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.
- The requirement and the prime's reach. What is the scope, and which parts of it does the prime perform well as core work? Where is the prime thin or absent?
- Past performance gaps. Where does the prime lack the recent, relevant past performance the solicitation will require?
- Set-aside and socioeconomic requirements. Is there a set-aside, a small-business subcontracting goal, or socioeconomic participation the team structure must satisfy?
- Candidate partners. Are there known or prospective teammates, and what does each bring?
- Constraints. Any incumbent subcontractors, existing relationships, exclusivity already in place, or known OCI concerns?
What ships with it
2 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.
- 10d ago First seen · 134 lines · 84 tokens per session scan A 118544b95e55
developing-teaming-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 84 tokens to every session and 1,504 once invoked, about $0.0004 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…
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…
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…
ot-cost-analysis
Trigger for: Other Transaction or OT should-cost, cost estimate, cost-share analysis, milestone pricing, funding profile, proposed-price comparison, prototype price analysis, research OT budget, production follow-on OT estimate, or OT price-reasonableness support under 10 U.S.C. 4021 or 4022. Build auditable…