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 market-research-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/market-research-workflow)<a href="https://agentmods.dev/skills/1102tools-dev/federal-contracting-skills/market-research-workflow"><img src="https://agentmods.dev/badge/skills/1102tools-dev/federal-contracting-skills/market-research-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/market-research-workflow"><img src="https://agentmods.dev/badge/skills/1102tools-dev/federal-contracting-skills/market-research-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 168 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 106 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.00159 | $0.05272 |
| Opus 5 | $0.00079 | $0.02636 |
| Sonnet 5 | $0.00032 | $0.01054 |
| Haiku 4.5 | $0.00016 | $0.00527 |
Grade A, and why
market-research-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 12d 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:
- market-research-workflow — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Research Workflow
Mandatory first response
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.
If status is missing_required, output this warning before the menu:
Data access readiness
- SAM.gov: SAM_API_KEY is not configured. It is required for SAM.gov entity, exclusion, opportunity, award, hierarchy, and subaward work. Other keyless research routes remain available.
- Setup: https://1102tools.com/setup#credentials
If the status operation is absent, output this warning 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. After any required readiness warning, output exactly this six-choice
block. Do not summarize it, rename options, omit an option, or use an alternate
condensed menu. A summarized, renamed, reordered, condensed, or incomplete menu is invalid.
What would you like to do?
1. Conduct quick market research and show the findings in chat
2. Build a complete FAR Part 10 market research report
3. Refresh or revise an existing market research report
4. Analyze one acquisition question or decision area
5. Prepare market-research findings for the Pre-Award Agent
6. Help me choose
When the opening request clearly maps to one choice, append (Recommended) to that choice only. End with exactly:
Which option would you like? You can reply with the number, label, or your own wording.
Then stop. The later Stage 1 section repeats this same canonical block as the workflow specification; it is not a different menu.
What ships with it
18 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 327 B
- references/analysis-methods.md 1.6 KB
- references/decision-boundaries.md 1.9 KB
- references/document-intake.md 2.2 KB
- references/evidence-contract.md 3.2 KB
- references/federal-data-operations.md 1.6 KB
- references/launch-menu-and-question-blocks.md 5.0 KB
- references/professional-product-standard.md 5.5 KB
- references/report-specification.md 6.1 KB
- references/runtime-adaptation.md 1.9 KB
- references/source-hierarchy.md 1007 B
- references/web-provider-policy.md 7.4 KB
- references/web-research-method.md 1.8 KB
- scripts/build_market_research_report.py 43 KB runs code
- scripts/validate_market_research_report.py 12 KB runs code
- scripts/validate_research_record.py 24 KB runs code
- test.md 6.2 KB
- testing.md 7.4 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.
- 12d ago First seen · 288 lines · 159 tokens per session scan A d524664d4cc8
market-research-workflow is a skill published in the GitHub repository 1102tools-dev/federal-contracting-skills (25 stars, last pushed 12d ago), licensed MIT. It adds 159 tokens to every session and 5,272 once invoked, about $0.0008 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
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…
reviewing-color-teams
Runs proposal color team reviews for a US Federal bid — Blue, Pink, Green, Red, Gold, and White Glove. Use when the user needs a color team review; a Blue, Pink, Green, Red, Gold, or White Glove (book check) review; a proposal or cost-volume review; an evaluator-perspective assessment; a mock evaluation; or a proposal…
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…