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 1102tools-dev/federal-contracting-skills --skill govcon-growth-workflowgit clone --depth 1 https://github.com/1102tools-dev/federal-contracting-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/1102tools-dev/federal-contracting-skills/govcon-growth-workflow)<a href="https://agentmods.dev/skills/1102tools-dev/federal-contracting-skills/govcon-growth-workflow"><img src="https://agentmods.dev/badge/skills/1102tools-dev/federal-contracting-skills/govcon-growth-workflow/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/1102tools-dev/federal-contracting-skills/govcon-growth-workflow"><img src="https://agentmods.dev/badge/skills/1102tools-dev/federal-contracting-skills/govcon-growth-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 81 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 130 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.04475 |
| Opus 5 | $0.00057 | $0.02237 |
| Sonnet 5 | $0.00023 | $0.00895 |
| Haiku 4.5 | $0.00012 | $0.00447 |
Grade A, and why
govcon-growth-workflow 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GovCon Growth Workflow
Purpose
Help federal contractors discover, qualify, understand, and pursue public-sector business using traceable evidence. Quick results remain in chat. Complete runs may produce a validated, route-specific .docx growth product.
Full workflows use SAM.gov, USASpending, and optional GSA CALC+ MCP servers, approved web access, and Python 3. Web research may use the optional Tavily remote MCP, the host's native search capabilities, or both. Tavily is never the sole supported path. DOCX briefs require python-docx and LibreOffice or an equivalent renderer. SAM is required only for SAM-specific modes; CALC+ is required only for pricing context.
This skill informs company decisions. It does not replace company leadership, legal, contracts, pricing, security, or compliance judgment.
Startup data-access readiness
On every new invocation, first call the sam-gov server's
get_access_status operation. This presence-only status call is the only MCP
call permitted before the menu and must not make an upstream request or reveal a
credential value.
For missing_required, show this block immediately before the menu:
Data access readiness
- SAM.gov: SAM_API_KEY is not configured. It is required for live opportunities, entities, registrations, exclusions, certifications, awards, hierarchy, and subaward work. Keyless USASpending and approved web routes remain available.
- Setup: https://1102tools.com/setup#credentials
If get_access_status is absent, show this block instead:
Data access readiness
- SAM.gov: Readiness could not be checked because get_access_status is missing. The SAM.gov MCP package or shared 1102tools host profile is outdated or incomplete. Update the installation, restart the client, and try again.
- Setup: https://1102tools.com/setup#credentials
For configured_unverified, do not claim that the key is valid and do not add a
warning. Never display, request, or transmit the credential value.
What ships with it
19 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.
- agents/openai.yaml 316 B
- references/brief-specification.md 10.0 KB
- references/competitor-intelligence.md 722 B
- references/evidence-contract.md 3.2 KB
- references/evidence-limitations.md 988 B
- references/launch-menu-and-question-blocks.md 5.9 KB
- references/market-and-agency-intelligence.md 743 B
- references/opportunity-intelligence.md 1.1 KB
- references/pricing-context.md 744 B
- references/professional-product-standard.md 5.5 KB
- references/recompete-radar.md 707 B
- references/runtime-adaptation.md 1.8 KB
- references/teaming-due-diligence.md 720 B
- references/web-provider-policy.md 7.4 KB
- scripts/build_growth_brief.py 23 KB runs code
- scripts/validate_growth_brief.py 12 KB runs code
- scripts/validate_research_record.py 24 KB runs code
- test.md 6.3 KB
- testing.md 4.9 KB
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 · 260 lines · 115 tokens per session scan A f288a38488d7
govcon-growth-workflow is a skill published in the GitHub repository 1102tools-dev/federal-contracting-skills (25 stars, last pushed 10d ago), licensed MIT. It adds 115 tokens to every session and 4,475 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
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…
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…
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-win-strategy
Develops the win strategy for a US Federal proposal. Use when the user needs win themes, discriminators, a win strategy, a value proposition, key messages, proposal themes, or ghosting language for a federal bid. Validates discriminators against a value-and-rarity test, builds substantiated win themes that connect…
estimating-price-to-win
Produces a price-to-win analysis for a US Federal opportunity. Use when the user needs price-to-win, PTW, a competitive pricing analysis, a price target or price range, or wants to understand pricing strategy, cost drivers, and pricing levers for a federal bid. Estimates the competitive price range and a target price…
planning-capture
Builds and maintains a living capture plan for a US Federal opportunity in the pre-RFP capture phase. Use when the user needs a capture plan, capture strategy, customer call plan, customer engagement or shaping plan, or wants to organize pre-RFP positioning work, intelligence gaps, teaming actions, and capture…