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 nasrulhazim/claude --skill project-faqgit clone --depth 1 https://github.com/nasrulhazim/claudeWrote 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/nasrulhazim/claude/project-faq)<a href="https://agentmods.dev/skills/nasrulhazim/claude/project-faq"><img src="https://agentmods.dev/badge/skills/nasrulhazim/claude/project-faq/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/nasrulhazim/claude/project-faq"><img src="https://agentmods.dev/badge/skills/nasrulhazim/claude/project-faq.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00152 | $0.02518 |
| Opus 5 | $0.00076 | $0.01259 |
| Sonnet 5 | $0.00030 | $0.00504 |
| Haiku 4.5 | $0.00015 | $0.00252 |
Grade A, and why
project-faq scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. **Include commands where relevant** — artisan commands, bash commands, curl examples How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Audience FAQ Generator
Researches a codebase comprehensively, then generates 7 audience-specific FAQ documents covering every stakeholder perspective — from C-suite executives to end users.
Trigger Detection
Activate when the user asks to generate FAQs, create a knowledge base, or build audience-specific Q&A documentation for a project.
Before generating anything:
- Ask for output path — where to write the FAQ documents (default:
docs/faq) - Ask for additional repositories — the user may have related repos (packages, ops, infrastructure) that should be researched alongside the main codebase
- Read CLAUDE.md if it exists — extract project context, architecture, conventions
- Read README.md — understand stated purpose and features
- Read composer.json / package.json — understand tech stack and dependencies
Interview Phase
Ask the user these questions before starting research:
Block 1 — Scope & Output
- Where should the FAQ documents be written? (default:
docs/faq) - Are there additional repositories to research? (e.g., core packages, ops/infra repos, reporting packages) — provide full paths
- What is the product name and company? (or auto-detect from CLAUDE.md / README.md)
Block 2 — Audience Selection (Optional)
- Which audiences do you need? (default: all 7)
- Business / Executive
- Marketing / Sales
- Project Manager
- Administrator
- Developer
- DevOps / Infrastructure
- API Consumer / End User
If the user says "all" or doesn't specify, generate all 7.
After confirming scope, proceed to research.
Research Phase
Phase 1: Deep Codebase Exploration (Parallel)
Launch parallel exploration agents — one per repository — to gather comprehensive information. Each agent should study:
| Area | What to Extract |
|---|---|
| Features & capabilities | All user-facing features, toggles, config options |
| Models & data schema | Database tables, relationships, key fields |
| User roles & permissions | Role definitions, permission naming, access control |
| Workflows & lifecycles | State machines, approval flows, automation |
| Commands & CLI | Artisan/CLI commands with descriptions |
| API endpoints | REST/GraphQL routes, authentication methods |
| Configuration | Config files, environment variables, defaults |
| Deployment & infrastructure | Server requirements, deployment scripts, architecture |
| Monitoring & reporting | Health checks, metrics, reporting tiers |
| Security | Auth methods, SSO, encryption, audit trails |
| Integrations | Third-party services, external systems |
| Notifications | Email, Slack, in-app notification events |
| Background services | Queue workers, schedulers, long-running processes |
| Troubleshooting patterns | Common errors, known gotchas, debugging commands |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 287 lines · 152 tokens per session scan A a4560693adb1
project-faq is a skill published in the GitHub repository nasrulhazim/claude (22 stars, last pushed 7d ago), licensed MIT. It adds 152 tokens to every session and 2,518 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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…