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 pnp/sharepoint-skills --skill rfp-response-content-generationgit clone --depth 1 https://github.com/pnp/sharepoint-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/pnp/sharepoint-skills/rfp-response-content-generation)<a href="https://agentmods.dev/skills/pnp/sharepoint-skills/rfp-response-content-generation"><img src="https://agentmods.dev/badge/skills/pnp/sharepoint-skills/rfp-response-content-generation/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/pnp/sharepoint-skills/rfp-response-content-generation"><img src="https://agentmods.dev/badge/skills/pnp/sharepoint-skills/rfp-response-content-generation.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 System Prompt Leakage · line 41 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00096 | $0.04207 |
| Opus 5 | $0.00048 | $0.02103 |
| Sonnet 5 | $0.00019 | $0.00841 |
| Haiku 4.5 | $0.00010 | $0.00421 |
Grade A, and why
rfp-response-content-generation 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 10d 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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Generation Skill
Firm Profile (REQUIRED — fill in before use)
These values define who your firm is and how it writes. See SETUP.md.
- FIRM NAME: [FIRM NAME]
- WHAT THE FIRM DOES: [one sentence]
- ROLE BOUNDARY: [what the firm will NOT claim to do — leave blank if none]
- VENDOR STANCE: [vendor-neutral OR resells/implements specific products]
- SPECIALIZATION: [domains the firm credibly claims]
- VALUE MODEL: [optional — the through-line your proposals argue]
- VOICE: [3–5 adjectives]
Purpose
This skill produces the proposal draft. It works section by section through the approved Table of Contents, grounding each section in source material from the RFP Tracker and capability library before writing. Every section has a specific source basis, a specific drafting instruction from the Content Strategy Brief, and a specific set of RFP requirements it must address. Where source material does not exist, it inserts a structured placeholder rather than inventing content. The output is a complete, structured Word document ready for Phase 4 review.
Critical Output Rules
Do not output any draft content to chat. The proposal draft is a document deliverable. All drafted content goes directly into the Word document saved in Step 7. Chat output is limited to one-line progress updates per section and the final summary. Never stream proposal content into chat.
Firm Position Boundary
Internalise these constraints before drafting any section. They apply to every word and cannot be overridden by source material or drafting instructions.
- Respect the ROLE BOUNDARY. If the firm advises but does not build/operate (or any similar boundary), match verbs to the role — "advise on", "design the approach for", "support your team to implement", not "build", "deploy", "operate". If the firm has no role boundary, skip this constraint.
- Respect the VENDOR STANCE. If vendor-neutral, never name, recommend, or imply preference for a specific product; if a client's RFP names a tool, acknowledge it neutrally. If the firm resells/implements products, position them as the Firm Profile allows.
- Stay within SPECIALIZATION. Do not claim expertise outside the firm's stated specialization unless source documents establish a credible track record.
- Do not name clients without explicit permission. Use anonymised descriptions ("a large public-sector organisation", "a national retailer").
- Do not invent proof points. If a statistic, outcome, or case study is not in the source documents, insert a placeholder — do not create a plausible-sounding version.
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.
- 10d ago First seen · 344 lines · 96 tokens per session scan A 3939c70e51f3
rfp-response-content-generation is a skill published in the GitHub repository pnp/sharepoint-skills (112 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 4,207 once invoked, about $0.0005 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
html-ppt-obsidian-claude-gradient
OpenDesign's enterprise AI-adoption brief: local-first agents at work, the risk controls, the ROI, and the rollout plan. Built as a decision-grade AI literacy deck for leadership, IT, security.
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
skill-deck
Generate slide deck presentations from briefs — use when you need slides, pitch decks, or visual summaries.
speech-to-text
Transcribe audio to text using ElevenLabs Scribe v2. Use when converting audio/video to text, generating subtitles, transcribing meetings, or processing spoken content.
msgraph-files
Read OneDrive and SharePoint files via the Microsoft 365 MCP server — list folder contents, fetch item metadata, inspect versions and sharing permissions. Use when locating a document in OneDrive/SharePoint, checking who a file is shared with, or reviewing file version history.
managedcode-markitdown
Use ManagedCode.MarkItDown when a .NET application needs deterministic document-to-Markdown conversion for ingestion, indexing, summarization, or content-processing workflows. USE FOR: ManagedCode.MarkItDown integration; document ingestion flows; Office or rich-text conversion to Markdown; indexing and summarization…