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 BlackBeltTechnology/pi-agent-dashboard --skill faq-minegit clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboardWrote 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/blackbelttechnology/pi-agent-dashboard/faq-mine)<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.
<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>- NVIDIA SkillSpector warn
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.
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.00094 | $0.03211 |
| Opus 5 | $0.00047 | $0.01605 |
| Sonnet 5 | $0.00019 | $0.00642 |
| Haiku 4.5 | $0.00009 | $0.00321 |
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.
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 evergreendocs/*.md.--docs skip= memory-only run (disables doc mining; the ship-change harvest path). - Optional
--memory <off|project|failures|all>— hermes stores to mine. Defaultfailures= project store + globalfailures.md(relevance-filtered).off= docs only.all= also globalMEMORY.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
- Read
docs/faq.mdif 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.
- If file missing, create with header:
- Enumerate candidate source docs (SKIP this whole step when
--docs skip— memory-only run):
Exclude:ls README.md docs/*.md 2>/dev/nulldocs/faq.mditselfdocs/faq.agent.md(condensed index derived FROM faq.md — refreshed in Phase 4, never mined)docs/AGENTS.mdand anyAGENTS.md(index, not narrative)docs/session-knowledge-*.md(point-in-time notes)docs/spec-gap-analysis.mdand any*-resolved.md(transient analyses)- Anything matching
docs/.faq-draft-*.md(in-flight draft)
- For each remaining doc, capture
wc -lto surface size. - 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$PROJdir absent (e.g. worktree name differs),ls ~/.pi/agent/projects-memory/and pick the matching dir; skip if none. - Global
pi-hermes-memory/failures.md— mixed 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).
- Project store
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.
- 11d ago First seen · 207 lines · 94 tokens per session scan A af6e8732b206
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.
Other skills, from other repositories
goga-cookbook
Principles for applying DSL specification in cell and CODEMANIFEST design.
goga-plan-by-design
Compile a design document into a ralphex execution plan.
goga-define-experience
Define the user experience required to achieve the established product goals and solve the identified problem.
goga-review-plan
Verify execution plan completeness and correctness.
goga-accept-manifest-review
Verify each Cell's CODEMANIFEST against the implementation.
goga-cells-by-brainstorm
Creation and modification of cells by architecture plan.