PM Skills is a collection of plain-Markdown instructions that teach AI assistants structured methods for handling professional, personal, and life-admin tasks. People use it with Claude, ChatGPT, Gemini, Cursor, Codex, and other supported agents for work such as writing product requirements, reviewing documents, or planning difficult situations.
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 mohitagw15856/pm-claude-skills --skill construction-rfi-responsegit clone --depth 1 https://github.com/mohitagw15856/pm-claude-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/mohitagw15856/pm-claude-skills/construction-rfi-response)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/construction-rfi-response"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/construction-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/skills/mohitagw15856/pm-claude-skills/construction-rfi-response"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/construction-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.00106 | $0.01288 |
| Opus 5.5 | $0.00042 | $0.00515 |
| Sonnet 5.5 | $0.00021 | $0.00258 |
| Haiku 4.5 | $0.00011 | $0.00129 |
Grade A, and why
construction-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 2d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Construction RFI Response
An RFI is a clock. Site is either waiting or proceeding on an assumption, and both are expensive. The answer that works is short, points at the document that governs, and says plainly whether this is a clarification or a change — because the argument that follows is almost always about that distinction, and it is far cheaper to settle in the response than in the final account.
What This Skill Produces
- A direct answer — the actual resolution, in the first line
- The governing reference — the drawing, specification clause, or schedule that supports it
- Cost and programme implication — stated explicitly, including when there is none
- Instruction status — whether this is a clarification of existing information or a variation requiring a formal instruction
- The distribution list — who else is affected and must receive it
- The register entry — the fields that keep the RFI log usable and the response auditable
Required Inputs
Ask for these if not provided:
- The RFI — the question as asked, its number, date received, and the response date required
- What is actually being asked — sometimes different from what was written; clarify before answering
- The governing documents — the drawings, specification, and schedules that bear on the question
- The status on site — whether work is stopped, proceeding, or about to be covered up
- Who else is affected — other trades, the client, and any consultant whose design is touched
Framework: Answer First, Reference Second, Implication Third
- Answer in the first line. Site reads the first sentence and acts. Context belongs underneath it.
- Point at the governing document. A drawing number and revision, or a specification clause. An answer with no reference generates the next RFI.
- Say whether this is a change. Clarification of existing information, or a variation? This single field is where most final-account disputes originate, and it costs nothing to state now.
- State the cost and time implication even when it is nil. 'No cost or programme implication' is a valuable sentence, and its absence is read as an admission.
- Answer what was actually asked. If the question is ambiguous, resolve the ambiguity by phone and record the clarification — do not answer a question you invented.
- Distribute to everyone affected. An answer that reaches only the asker creates a second RFI from another trade.
- Watch the clock. If you cannot answer in full by the required date, issue a holding response with a date — silence is what causes the delay claim.
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.
- 2d ago First seen · 86 lines · 106 tokens per session scan A f238740d9001
construction-rfi-response is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 106 tokens to every session and 1,288 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-10-12.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…