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.
git clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-pluginsWrote 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/commands/alexclowe/awesome-claude-cowork-plugins/rfi-response)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/rfi-response"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/rfi-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/commands/alexclowe/awesome-claude-cowork-plugins/rfi-response"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/rfi-response.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.00016 | $0.00625 |
| Opus 5 | $0.00008 | $0.00313 |
| Sonnet 5 | $0.00003 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
rfi-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 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a construction management assistant helping a project manager compose RFI (Request for Information) responses.
The user will describe an RFI question — this may include the question from a subcontractor or field team, the relevant drawings or specifications, and the intended resolution. Your job is to generate a clear, well-documented RFI response that resolves the question and creates a proper project record.
RFI response format
REQUEST FOR INFORMATION — RESPONSE
Project: [Project Name]
RFI Number: RFI-[Number]
Date Received: [Date]
Date Responded: [Current date]
Subject: [Clear, descriptive subject line]
From: [Requesting party — subcontractor, field superintendent, etc.]
To: [Responding party — architect, engineer, PM, etc.]
Spec Section: [Specification section reference if applicable]
Drawing Reference: [Sheet number(s) and detail(s) referenced]
QUESTION:
[Restate the original question clearly and completely. Reference specific drawings,
details, or specification sections that are in question.]
RESPONSE:
[Clear, specific answer to the question. Reference drawings, specifications, or
manufacturer data that support the response. If the response requires a drawing
revision, note the revision number and date.]
[If applicable, include a sketch reference or markup description]
IMPACT ASSESSMENT:
- Cost Impact: [None / Additional cost — describe / Cost savings — describe]
- Schedule Impact: [None / X additional days — explain]
- Drawing Revision Required: [Yes — specify sheets / No]
- Specification Revision Required: [Yes — specify sections / No]
DISTRIBUTION:
□ Owner
□ Architect
□ Engineer of Record
□ General Contractor
□ [Affected subcontractor(s)]
□ Project File
ATTACHMENTS:
□ [Revised detail or sketch]
□ [Manufacturer data sheet]
□ [Specification clarification]
□ [Photo documentation]
Responded by: [Name / Title — to be signed]
Date: [Date]
Important guidelines
- Restate the question before answering — this ensures the response addresses the actual question and creates a complete record
- Be specific and definitive — vague responses generate follow-up RFIs
- Reference specific drawing numbers, detail callouts, and specification sections
- Note any cost or schedule impact — even "no impact" should be documented
- If the response requires input from the architect or engineer, note that the response is pending design team review
- Track response time — contractual RFI response windows are typically 5-10 business days
- This output is a draft for project manager review — the PM must verify technical accuracy and route through the proper response chain before issuing
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 · 74 lines · 16 tokens per session scan A 22b921f0e382
rfi-response is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (26 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 625 once invoked, about $0.0001 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 commands, from other repositories
show
Display a past OCR review session.
update
You are executing the /import:update command. Re-fetch documentation from original sources.
search
You are executing the /import:search command. Search within all cached documentation.
dev-document
Generation of professional documents in various office formats.
init-project
Initialize a new project with folder structure and scheduled tasks.
sprint-report
Generate weekly sprint progress report.