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 Notysoty/openagentskills --skill faq-generatorgit clone --depth 1 https://github.com/Notysoty/openagentskillsWrote 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/notysoty/openagentskills/faq-generator)<a href="https://agentmods.dev/skills/notysoty/openagentskills/faq-generator"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/faq-generator.svg" alt="Measured on agentmods" 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.00019 | $0.01623 |
| Opus 5 | $0.00010 | $0.00812 |
| Sonnet 5 | $0.00004 | $0.00325 |
| Haiku 4.5 | $0.00002 | $0.00162 |
Grade A, and why
FAQ Generator 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 8d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FAQ Generator
What this skill does
This skill generates a comprehensive, well-structured FAQ section for any product, API, feature, or documentation page. It anticipates the questions real users ask (not the questions you wish they'd ask), groups them logically, and writes clear, direct answers that actually resolve the doubt rather than redirecting to other pages. The output is ready to paste into documentation, a help center, or a landing page.
Use this when launching a new product or feature, when your support team keeps answering the same questions, when you want to reduce friction for new users, or when you're writing documentation and want to anticipate objections.
How to use
Claude Code / Cline
Copy this file to .agents/skills/faq-generator/SKILL.md in your project root.
Then ask:
- "Use the FAQ Generator skill to write FAQs for our authentication API."
- "Generate an FAQ for the pricing page using the FAQ Generator skill."
Provide:
- A description of the product, API, or feature
- Any existing documentation, landing page copy, or support tickets (these reveal real questions)
- The target audience (developers, end users, business buyers, etc.)
- Any specific questions you know are common
Cursor
Add the instructions below to your .cursorrules or paste them into the Cursor AI pane. Provide the product description and any source material.
Codex
Paste the product description or documentation and ask Codex to follow the instructions below to generate the FAQ.
The Prompt / Instructions for the Agent
When asked to generate FAQs, follow these steps:
Step 1 — Understand the subject
Before writing, identify:
- What is this product/API/feature and what does it do?
- Who is the target audience?
- What is the key value proposition?
- What are the most common points of confusion or hesitation for this type of product?
- Are there any support tickets, reviews, or forum posts that reveal real user questions?
Step 2 — Generate questions from multiple angles
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.
- 8d ago First seen · 184 lines · 19 tokens per session scan A e1ed3d47796e
FAQ Generator is a skill published in the GitHub repository Notysoty/openagentskills (9 stars, last pushed 24d ago), licensed MIT. It adds 19 tokens to every session and 1,623 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-31.
Other skills, from other repositories
interface-auditor
Detect UX antipatterns (smells) in interface descriptions using the uxuiprinciples smell taxonomy. Returns structured findings with matched symptoms, severity, and step-by-step remediation recipes. API key optional — full remediation recipes require uxuiprinciples.com API Access.
uxui-evaluator
Evaluate interface descriptions against 195 research-backed UX/UI principles. Returns structured findings with severity, remediation, and business impact. API key optional — enriched output requires uxuiprinciples.com API Access.
goose-graphics-create-style
End-to-end skill that turns a single reference image into a published Gooseworks style — analyzes the image, drafts the slim style spec, renders a hero example plus 2-3 additional formats via Playwright, writes the gooseworks-style.json manifest, and publishes via npx gooseworks styles publish so other agents can…
goose-graphics-create-format
Creates a new graphics format spec (custom canvas dimensions + content rules) and publishes it to the Gooseworks library so any agent can render against it. Use when the existing community formats (carousel, story, infographic, slides, poster, chart, tweet, plus community additions) don't fit the user's canvas — e.g.…
frontend
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…