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 britt/agent-skills --skill build-faq-from-issuesgit clone --depth 1 https://github.com/britt/agent-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/britt/agent-skills/build-faq-from-issues)<a href="https://agentmods.dev/skills/britt/agent-skills/build-faq-from-issues"><img src="https://agentmods.dev/badge/skills/britt/agent-skills/build-faq-from-issues/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/britt/agent-skills/build-faq-from-issues"><img src="https://agentmods.dev/badge/skills/britt/agent-skills/build-faq-from-issues.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.00048 | $0.00691 |
| Opus 5 | $0.00024 | $0.00345 |
| Sonnet 5 | $0.00010 | $0.00138 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
build-faq-from-issues 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build FAQ from Issues Skill
Extract common questions from closed GitHub issues and generate a structured FAQ document with answers and source links.
When to Use
Activate when:
- Creating or updating a project FAQ
- Documenting common support questions
- Reducing repeat questions in issues
- Onboarding new users/contributors
When NOT to use: not for open-issue triage, changelogs or release notes, or repos with too few closed issues to find recurring patterns.
Workflow
Prerequisite: requires the gh CLI authenticated to the target repository.
- List closed issues:
gh issue list --state closed --limit 200 --json number,title,labels,url. Optionally filter by question/support labels (e.g.--label question). - Read resolutions for candidate issues with
gh issue view <n> --commentsto find the accepted answer or fix. - Group recurring questions — cluster issues that ask the same thing into a single candidate FAQ entry.
- Synthesize a standalone answer for each entry from the clearest resolution.
- Emit the FAQ using the template below.
Output Structure
## FAQ: [Project/Topic]
**Generated from**: [X closed issues] | **Labels**: [question, help, support]
### General
#### Q: [Common question]
[Answer synthesized from issue resolution]
— See #123
#### Q: [Another question]
[Answer]
— See #456
### Setup & Installation
#### Q: [Setup question]
[Answer with steps if needed]
— See #789
### Troubleshooting
#### Q: [Error or problem question]
[Answer with solution]
— See #101
### Configuration
#### Q: [Config question]
[Answer]
— See #202
Guidelines
Question Selection
- Focus on closed/resolved issues
- Prioritize issues labeled:
question,help,support,faq - Include frequently recurring questions
- Skip one-off bugs or feature requests
Answer Quality
- Write standalone answers (don't require reading the issue)
- Include concrete steps when applicable
- Keep answers concise but complete
- Link to docs if more detail exists elsewhere
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 · 117 lines · 48 tokens per session scan A 28e8c7eaa6dc
build-faq-from-issues is a skill published in the GitHub repository britt/agent-skills (5 stars, last pushed 6d ago), licensed MIT. It adds 48 tokens to every session and 691 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…