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 acquisition-policy-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/acquisition-policy-workflow)<a href="https://agentmods.dev/skills/1102tools-dev/federal-contracting-skills/acquisition-policy-workflow"><img src="https://agentmods.dev/badge/skills/1102tools-dev/federal-contracting-skills/acquisition-policy-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/acquisition-policy-workflow"><img src="https://agentmods.dev/badge/skills/1102tools-dev/federal-contracting-skills/acquisition-policy-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 122 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.03947 |
| Opus 5 | $0.00057 | $0.01973 |
| Sonnet 5 | $0.00023 | $0.00789 |
| Haiku 4.5 | $0.00012 | $0.00395 |
Grade A, and why
acquisition-policy-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- acquisition-policy-workflow — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Acquisition Policy Workflow
Purpose
Explain and trace published federal acquisition policy with an explicit as-of date, source hierarchy, and documented-status boundary. Support concise sourced chat answers and, when a written product is requested, a route-specific .docx for government, industry, or neutral audiences.
The complete workflow uses the eCFR, Federal Register, Regulations.gov, and Acquisition.gov MCP servers. Use only the capabilities required by the selected mode. Do not substitute direct HTTP, shell requests, or a general web provider for a missing required MCP.
Startup data-access readiness
On every new invocation, first call the regulations-gov server's
get_access_status operation. This is a local, presence-only status call; it
must not contact Regulations.gov or reveal a credential value.
For limited_fallback, show this block before the routed mode or menu:
Data access readiness
- Regulations.gov: REGULATIONS_GOV_API_KEY is not configured. Docket and public-comment research will use the shared DEMO_KEY fallback, limited to approximately 10 requests per hour.
- Setup: https://1102tools.com/setup#credentials
If get_access_status is absent, show this block instead:
Data access readiness
- Regulations.gov: Readiness could not be checked because get_access_status is missing. The Regulations.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.
Read supporting files only when their stage is reached:
- launch-menu-and-framing.md for mode routing, route outcomes, Help diagnosis, and exact framing questions.
- document-intake.md when the user supplies policy files, paths, or pasted text.
- source-routing.md before planning or retrieving evidence.
- status-and-decision-boundaries.md before classifying policy status or presenting findings.
- evidence-contract.md whenever creating or updating the policy-research record.
- professional-product-standard.md before drafting any reader-facing response or file.
- report-specification.md before generating a brief.
- runtime-adaptation.md when capabilities, files, or document tooling differ by host.
What ships with it
14 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 281 B
- references/document-intake.md 1.5 KB
- references/evidence-contract.md 4.7 KB
- references/launch-menu-and-framing.md 7.5 KB
- references/professional-product-standard.md 5.5 KB
- references/report-specification.md 12 KB
- references/runtime-adaptation.md 1.4 KB
- references/source-routing.md 3.8 KB
- references/status-and-decision-boundaries.md 3.9 KB
- scripts/build_acquisition_policy_brief.py 65 KB runs code
- scripts/validate_acquisition_policy_brief.py 16 KB runs code
- scripts/validate_policy_research_record.py 25 KB runs code
- test.md 1.6 KB
- testing.md 2.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 · 234 lines · 115 tokens per session scan A 87da954bee53
acquisition-policy-workflow is a skill published in the GitHub repository 1102tools-dev/federal-contracting-skills (25 stars, last pushed 9d ago), licensed MIT. It adds 115 tokens to every session and 3,947 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
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.…
shredding-solicitations
Shreds a US Federal solicitation into a requirements and compliance matrix. Use when the user needs to shred or analyze an RFP, RFQ, RFI, or task order, build a compliance matrix or requirements matrix, extract shall statements, or cross-walk Section L instructions, Section M evaluation factors, and the Section…
Acquisition Diligence Request List
Use when generating a tailored M&A due-diligence request list, organized by workstream, for a buyer or seller in an acquisition.
compliance-audit
Audits codebases against compliance frameworks (SOC2, HIPAA, PCI-DSS, GDPR, ISO27001, etc.) using parallel agents per subdirectory/sub-repo. Produces a detailed markdown report with line-level code references. Use when you need to check a directory or monorepo for compliance violations before an audit or review.
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…