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 agentmods add skills/sananthanarayan/skilldrop/prfaqnpx skills add sananthanarayan/skilldrop --skill prfaqgit clone --depth 1 https://github.com/sananthanarayan/skilldropWrote 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/sananthanarayan/skilldrop/prfaq)<a href="https://agentmods.dev/skills/sananthanarayan/skilldrop/prfaq"><img src="https://agentmods.dev/badge/skills/sananthanarayan/skilldrop/prfaq.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 | $0.00083 | $0.01793 |
| Opus 5 | $0.00042 | $0.00897 |
| Sonnet 5 | $0.00017 | $0.00359 |
| Haiku 4.5 | $0.00008 | $0.00179 |
Grade A, and why
prfaq 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 4d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
prfaq
The working-backwards forcing function: write the launch press release before the product exists, then answer the questions a real customer and a skeptical insider would ask. If the press release can't be written specifically — a nameable customer, a problem in their words, a benefit you could measure — the product isn't ready to spec, and surfacing that is the deliverable. Sits upstream of prd-draft (requirements for a committed product) and business-case (invest/defer decision): the PRFAQ decides whether the idea deserves either.
How to respond
-
Pin the three anchors — customer, problem, differentiator. Ask at most 2 questions, spent on the weakest anchors: "Who exactly is the customer, and what do they do today instead?" and "What does this do that the thing they use today doesn't?" A PRFAQ for "everyone" with a problem stated in industry jargon produces a marketing document, not a forcing function — don't start drafting until all three anchors are concrete. Non-interactive run (no user to ask): derive missing anchors from the input where defensible and tag them
[assumption]at the top; an anchor with no defensible derivation → emitBLOCKED: need <anchor>naming what to rerun with, instead of fabricating a customer. -
Write the press release — one page, datelined with a city and a realistic launch date; no product name exists yet → invent a plausible working name and mark it as a placeholder. The blocks:
- Headline: product name + the customer benefit in one sentence. ✅ "Acme Contracts cuts routine contract review from three days to twenty minutes for in-house legal teams" — ❌ "Acme launches AI-powered legal platform".
- Sub-headline: the one key detail the headline compressed (who it's for, what it replaces, or the mechanism).
- Problem paragraph: the customer's current pain in their words. ✅ "I can't close a deal until legal clears the paperwork, and legal is three days behind" — ❌ "lack of operational visibility into contract workflows".
- Solution paragraph: what the product does and what it does differently from the alternative the customer already uses. "AI-powered" is not a differentiator; the mechanism is.
- Leadership quote: one sentence naming the strategic rationale, attributed to a role ("our VP of Product"), never a placeholder name. If the rationale can't be articulated, that's a finding — report it.
- Customer quote: a named-persona customer describing the before/after in concrete terms — a specific moment, not adjectives.
- Call to action: what the customer does next to get started.
What ships with it
4 files 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.
- 4d ago First seen · 76 lines · 83 tokens per session scan A ef05e166a6fd
prfaq is a skill published in the GitHub repository sananthanarayan/skilldrop (2 stars, last pushed 21d ago), licensed MIT. It adds 83 tokens to every session and 1,793 once invoked, about $0.0004 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
openlore-plan-refactor
Identify a high-priority refactoring target, assess its blast radius, and write .openlore/refactor-plan.md without changing code. Use when asked to plan or prioritize a refactor.
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
openlore-debug
Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.
openlore-execute-refactor
Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.
openlore-analyze-codebase
Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.
team-repair
Re-index OKF v0.2 index.md/log.md files, derive CDR.md, rebuild .skills.json and AGENTS.md in team-ai-directives, migrate v0.1→v0.2 frontmatter, scan for rule conflicts, and verify directive freshness. Use when indexes are inconsistent, orphans are detected, after bulk changes, or for periodic team AI directives…