faq-mine

faq-mine is a skill for Claude Code, Codex from BlackBeltTechnology/pi-agent-dashboard. It costs 94 tokens per session (3,211 once invoked), scanned A, original, MIT.

A documentation tool that builds or updates an FAQ file from project documents and stored records of past runtime problems.

In plain words
What is it for?
Use it to create, regenerate, or extend docs/faq.md from README.md, other Markdown documents, and selected pi-hermes memory stores.
Why use it?
It collects common questions and fixes that might otherwise remain scattered across documentation or be rediscovered repeatedly.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; mentions AGENTS.md.

Good fit Use it to create, regenerate, or extend docs/faq.md from README.md, other Markdown documents, and selected pi-hermes memory stores.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/blackbelttechnology/pi-agent-dashboard/faq-mine
Install

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.

Any agent
npx skills add BlackBeltTechnology/pi-agent-dashboard --skill faq-mine
Clone the repo
git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for faq-mine

README.md
[![agentmods](https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/faq-mine/github.svg)](https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/faq-mine)
Your own site
<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/faq-mine"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/faq-mine/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.

agentmods 80×15 button for faq-mine

Your own site · 80×15
<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/faq-mine"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/faq-mine.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 94 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,211 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 4 findings, 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 Tool Misuse · line 170
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • medium Rogue Agent · line 3
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
  • medium Rogue Agent · line 32
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
  • medium Rogue Agent · line 175
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00094 $0.03211
Opus 5 $0.00047 $0.01605
Sonnet 5 $0.00019 $0.00642
Haiku 4.5 $0.00009 $0.00321

Measured 11d ago against content hash af6e8732b206, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

faq-mine 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 11d 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.

packages/authoring-toolkit/.pi/skills/faq-mine/SKILL.md · 207 lines

How it starts

The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Orchestrate FAQ extraction from project knowledge docs AND pi-hermes memory stores into docs/faq.md.

Two source classes:

  • Docs — README.md + evergreen docs/*.md. How-to / what-is questions.
  • Hermes memory — accumulated runtime problems (tool-quirks, failures, insights, corrections) that never reach the docs. These carry the "why does X fail / how do I fix Y" answers a future agent keeps re-discovering.

Inputs:

  • Optional --docs <a.md>,<b.md> — explicit doc list. Default = README.md + every evergreen docs/*.md. --docs skip = memory-only run (disables doc mining; the ship-change harvest path).
  • Optional --memory <off|project|failures|all> — hermes stores to mine. Default failures = project store + global failures.md (relevance-filtered). off = docs only. all = also global MEMORY.md.
  • Optional --max <N> — entry cap per source (default ~10).

Non-interactive: passing BOTH --docs (incl. --docs skip) and --memory skips the Phase 1 prompt — the headless invocation faq-mine --docs skip --memory failures runs memory-only with no ask_user.


Phase 0 — Pre-flight

  1. Read docs/faq.md if it exists. Extract every ## <Question> heading into a dedupe list.
    • If file missing, create with header:
      # FAQ
      
      FAQ. How-to answers that already live in README.md + docs/. New entries here when same question recurs.
      
  2. Enumerate candidate source docs (SKIP this whole step when --docs skip — memory-only run):
    ls README.md docs/*.md 2>/dev/null
    
    Exclude:
    • docs/faq.md itself
    • docs/faq.agent.md (condensed index derived FROM faq.md — refreshed in Phase 4, never mined)
    • docs/AGENTS.md and any AGENTS.md (index, not narrative)
    • docs/session-knowledge-*.md (point-in-time notes)
    • docs/spec-gap-analysis.md and any *-resolved.md (transient analyses)
    • Anything matching docs/.faq-draft-*.md (in-flight draft)
  3. For each remaining doc, capture wc -l to surface size.
  4. Enumerate hermes memory stores (unless --memory off):
    PROJ=$(basename "$(git rev-parse --show-toplevel)")
    ls -l "$HOME/.pi/agent/projects-memory/$PROJ/MEMORY.md" \
          "$HOME/.pi/agent/pi-hermes-memory/failures.md" \
          "$HOME/.pi/agent/pi-hermes-memory/MEMORY.md" 2>/dev/null
    
    • Project store projects-memory/$PROJ/MEMORY.md — all entries repo-scoped, no filter. If $PROJ dir absent (e.g. worktree name differs), ls ~/.pi/agent/projects-memory/ and pick the matching dir; skip if none.
    • Global pi-hermes-memory/failures.mdmixed across projects, needs a repo-relevance filter (subagent applies it).
    • Global pi-hermes-memory/MEMORY.md — mixed, only when --memory all.
    • Any store path that does not exist: skip silently (fresh machine).

Read the full file on GitHub · 207 lines

Files

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.

Changes

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.

  1. 11d ago First seen · 207 lines · 94 tokens per session scan A af6e8732b206

Subscribe to this mod's changes

faq-mine is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (279 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 3,211 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.