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 swan-gtm/gtm-skills --skill rfp-responsegit clone --depth 1 https://github.com/swan-gtm/gtm-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/swan-gtm/gtm-skills/rfp-response)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/rfp-response"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/rfp-response/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/swan-gtm/gtm-skills/rfp-response"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/rfp-response.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Anti-Refusal · line 44 Skill instructs the agent to never refuse or to always comply. Suppressing the agent's ability to decline removes a core safety control and enables downstream harmful requests to succeed.Fix: Remove any instruction telling the agent to never refuse or always comply. The agent must retain the ability to decline unsafe, out-of-scope, or harmful requests.
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.00135 | $0.01139 |
| Opus 5 | $0.00068 | $0.00570 |
| Sonnet 5 | $0.00027 | $0.00228 |
| Haiku 4.5 | $0.00014 | $0.00114 |
Grade A, and why
rfp-response 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 9d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Applies from the moment a request for proposal lands until the proposal is submitted and tracked. Produces a qualify decision, a response built to how the buyer will actually score it, a deadline-driven work plan, and a pipeline status read.
An RFP is a timed exam someone else wrote. Two things lose winnable deals: bidding on the ones you were never going to win, and losing track of the clock on the ones you could. This skill front-loads the qualify decision so effort goes where it can pay off, then keeps every live RFP visible against its deadline.
Qualify before you invest
Before anyone writes a slide, decide whether to bid. A response is expensive; a reflexive yes to every RFP burns the team and lowers the win rate on the ones that mattered. Score fit, winnability, and whether the request is even real (some RFPs exist to justify an incumbent already chosen). The bid/no-bid rubric, the disqualifiers, and how to route ownership once you commit are in references/qualify-and-route.md.
Anchor on the deadline, not the flight dates
Read the request for the one date that governs everything: when the proposal is due. Keep it separate from the campaign or engagement dates the RFP also lists - people routinely record the flight dates as the deadline and miss the submission by a week. Put the proposal deadline at the top of every working artefact, above the engagement dates, so no one has to hunt for it.
Structure the response to the scorecard
Buyers score RFPs against stated (and unstated) criteria; the response is built to that scorecard, not to your standard pitch. Answer every question they asked, fully, in their order; lead each section with the criterion it satisfies; and start from a clean canonical template, never from the last deal's response. The full response structure, the "answer what they asked" discipline, and why you never reuse a previous RFP's deck are in references/response-structure.md.
Work backward from the deadline
Sequence the work from the due date, not forward from today. Identify the long-pole items (custom pricing, creative, security or legal review, exec sign-off), start those first, and leave a buffer for the review round that always runs late. Nothing goes out without a human owner approving the final submission. The reverse timeline, the long-pole checklist, and the status model are in references/timeline-and-status.md.
What ships with it
3 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.
- 9d ago First seen · 48 lines · 135 tokens per session scan A 4ecde29f2ec7
rfp-response is a skill published in the GitHub repository swan-gtm/gtm-skills (150 stars, last pushed 2d ago), licensed MIT. It adds 135 tokens to every session and 1,139 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
Pipedrive Automation
Automate Pipedrive CRM workflows including deal management, pipeline tracking, and sales reporting.
afrexai-lead-hunter
Enterprise-grade B2B lead generation, enrichment, scoring, and outreach sequencing for AI agents. Find ideal prospects, enrich with verified data, score against your ICP, and generate personalized outreach — all autonomously.
proposals
Use when writing the document a buyer reads to say yes — a commercial proposal or Statement of Work, turning discovery notes into a scoped and priced document, adding tiers so the middle one wins, or diagnosing a proposal that will not close. NOT the binding legal agreement with its liability and IP clauses (that is…
co-founder-dynamics
Complete co-founder playbook for technical founders — finding co-founders, equity splits (dynamic and static), co-founder agreements, vesting schedules, working relationships, conflict resolution, co-founder breakups, and the "dating before marrying" framework. Use when looking for a co-founder, structuring a founding…
support-tool-stack
Customer support platform selection, setup, and optimization — Intercom, Zendesk, Front, Help Scout, HubSpot Service Hub, Linear, and AI-native tools. Use when choosing a support platform, migrating tools, setting up help desk workflows, designing ticket routing, building macros and saved replies, or integrating…
advisor-recruitment
Strategic advisor recruitment for B2B SaaS founders. Use when building advisory board, recruiting individual advisors, structuring advisor compensation (equity grants), defining advisory scope, leveraging advisors for intros/references/customers, and managing ongoing advisor relationships.