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 checking-submission-compliancegit 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/checking-submission-compliance)<a href="https://agentmods.dev/skills/danielkinneyspears/federal-proposal-skills/checking-submission-compliance"><img src="https://agentmods.dev/badge/skills/danielkinneyspears/federal-proposal-skills/checking-submission-compliance/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/checking-submission-compliance"><img src="https://agentmods.dev/badge/skills/danielkinneyspears/federal-proposal-skills/checking-submission-compliance.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.00097 | $0.01769 |
| Opus 5.5 | $0.00039 | $0.00708 |
| Sonnet 5.5 | $0.00019 | $0.00354 |
| Haiku 4.5 | $0.00010 | $0.00177 |
Grade A, and why
checking-submission-compliance 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checking Submission Compliance
Run the last check before the proposal is submitted. A technically excellent proposal can still be thrown out for a format technicality — an over-length volume, a missing certification, price information in the wrong file, a late upload. The government can and does reject non-conforming proposals without evaluating them. This skill verifies, methodically, that the proposal will be accepted and evaluated.
When to use this skill
Use this skill at the end of the proposal process, after the Gold Team and before submission. Run it on the final or near-final proposal package.
It is not a content review — reviewing-color-teams assesses whether the
proposal is good. This skill assesses whether the proposal is conforming: will
it be accepted, opened, and evaluated rather than rejected.
Inputs
Required:
- The final proposal package — every volume and file intended for submission.
10-compliance-matrix.md, including its format and submission register.- The solicitation Sections L and K, and any submission instructions or portal guidance.
Preferred upstream artifacts:
20-color-review-*.md: to confirm color team findings were resolved.
Read ../../shared/glossary.md,
../../shared/federal-solicitation-primer.md, and
../../shared/pursuit-workspace.md if not already read this session.
Intake
Ask these as a numbered list. Most answers come from the compliance matrix's format register and Section L.
- The package. What files make up the submission package, and which volume does each represent? Is the package final?
- Format rules. What are the page limits per volume, and the font, point size, margin, and spacing rules? What counts toward and is excluded from page limits?
- File rules. What file formats, file-naming conventions, and file-size limits does Section L impose? What volume-separation rules apply (for example, price kept out of the technical volume)?
- Forms and certifications. What forms, representations, and certifications does the solicitation require (Section K, the cover form, any solicitation-specific certifications)? Is the offeror's SAM.gov registration active?
- Submission mechanics. How, where, and by exactly when must the proposal be submitted — portal, email, or physical; the due date, time, and time zone; any required pre-registration?
What ships with it
5 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 · 160 lines · 97 tokens per session scan A f23950d0afcc
checking-submission-compliance is a skill published in the GitHub repository danielkinneyspears/federal-proposal-skills (8 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 97 tokens to every session and 1,769 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.
checking-submission-compliance compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| checking-submission-compliancedanielkinneyspears/federal-proposal-skills | Skill | 8 | 3mo ago | Apache-2.0 | A | 97 | 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 |
| igce-builder-cr1102tools-dev/federal-contracting-skills | Skill | 25 | 2mo ago | MIT | A | 161 | Codex |
| acquisition-policy-workflow1102tools-dev/federal-contracting-skills | Skill | 25 | 2mo ago | MIT | A | 115 | Codex |
| ot-project-description-builder1102tools-dev/federal-contracting-skills | Skill | 25 | 2mo ago | MIT | A | 185 | Codex |
| sow-pws-builder1102tools-dev/federal-contracting-skills | Skill | 25 | 2mo ago | MIT | A | 133 | Codex |