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 paruff/uFawkesAI --skill discoverygit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/discovery)<a href="https://agentmods.dev/skills/paruff/ufawkesai/discovery"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/discovery/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/paruff/ufawkesai/discovery"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/discovery.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.00050 | $0.01725 |
| Opus 5 | $0.00025 | $0.00863 |
| Sonnet 5 | $0.00010 | $0.00345 |
| Haiku 4.5 | $0.00005 | $0.00172 |
Grade A, and why
discovery 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Discovery
Load trigger:
"load discovery skill"> DORA: AI Capability 6 (User-centric focus) Token cost: Low
Purpose
A 15-minute structured exercise that surfaces the real user need behind a proposed
change, the riskiest assumption embedded in it, and one testable acceptance criterion.
Output is discovery-brief.md — mandatory input to the spec agent.
DORA AI Capabilities Model v2025.1: Teams adopting AI without user-centric focus see harm to team performance. Speed is irrelevant if moving in the wrong direction.
When to Run
| Situation | Run discovery? |
|---|---|
| New feature proposed | ✅ Always |
| Infrastructure migration that affects developer workflow | ✅ Yes — the developer is the user |
| Bug fix | ⚠ Only if the fix changes user-visible behavior |
| Dependency update, doc fix, test addition | ❌ Skip — no user behavior change |
| New Dojo belt module | ✅ Yes — the learner is the user |
Persona Reference Table
| Persona ID | Role | Primary job | Pain points |
|---|---|---|---|
platform-engineer |
You (paruff) | Ship reliable IDP improvements in 2hrs/day | Context switching, migration blast radius, scope creep |
product-engineer |
Dev using fawkes golden paths | Get from idea to running service | Unclear golden paths, config complexity, slow feedback loops |
dojo-learner |
Developer learning DevOps/platform skills | Learn by doing, not reading | Labs that don't run, missing prerequisites, unclear outcomes |
team-lead |
Engineering manager adopting fawkes | Know if the platform investment pays off | No DORA visibility, unclear ROI, onboarding friction |
solo-entrepreneur |
Small-team founder using uFawkesPipe/uFawkesObs | Ship product, not manage infra | Operational overhead, complex setup, limited time |
What ships with it
3 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.
- 9d ago First seen · 195 lines · 50 tokens per session scan A cd60f42f18ac
discovery is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 16d ago), licensed MIT. It adds 50 tokens to every session and 1,725 once invoked, about $0.0003 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
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
infrastructure-overview
Top-level skill for the research template infrastructure layer. Use in Cursor, Claude Code, or similar agents when editing or importing anything under infrastructure/, understanding the two-layer architecture, or wiring build/validation/rendering/publishing. Covers module discovery, import patterns, thin…
infrastructure-validation
Skill for the validation infrastructure module providing PDF validation, markdown validation, output integrity checks, link verification, documentation audits, issue categorization, and repository scanning. Use when validating research outputs, checking document quality, running audits, or verifying cross-references.
infrastructure-llm
Skill for the LLM infrastructure module providing local Large Language Model integration via Ollama. Covers client initialization, prompt templates, output validation, manuscript review generation, conversation context, and CLI usage. Use when querying LLMs, generating manuscript reviews, validating LLM outputs, or…
research-workflow
Seven-stage research workflow (SCOPE→LITERATURE→REASON→DESIGN→COMPUTE→SYNTHESIZE→WRITE). Use for: structuring an AI agent's research process, generating literature review prompts, scoping methodology. Usage: from infrastructure.research import ResearchWorkflow; ResearchWorkflow.describe() Config: set stage overrides…
infrastructure-search-literature
Paperclip-style multi-source literature search across arXiv, Crossref, local JSON corpora, and (opt-in) the Paperclip API. Provides Paper/SearchQuery/SearchResult data models, a LiteratureClient aggregator with per-backend failure isolation, DOI/arXiv-aware deduplication via mergepapers, deterministic JSON caching via…