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 roi-reportinggit 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/roi-reporting)<a href="https://agentmods.dev/skills/paruff/ufawkesai/roi-reporting"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/roi-reporting/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/roi-reporting"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/roi-reporting.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.00062 | $0.02036 |
| Opus 5 | $0.00031 | $0.01018 |
| Sonnet 5 | $0.00012 | $0.00407 |
| Haiku 4.5 | $0.00006 | $0.00204 |
Grade A, and why
roi-reporting 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: ROI Reporting
Load trigger:
"load roi-reporting skill"> DORA: AI Capability 2 (Healthy data ecosystems) + AI Capability 7 (Quality internal platforms) Token cost: Low–Medium Prerequisite:dora-measurementsnapshot for the period must exist.
Purpose
Translate DORA metric numbers into business language that answers the question every stakeholder actually asks: "Is this platform investment worth it?"
DORA ROI 2026: ROI is measured by how much latent human creativity is unlocked by offloading systemic toil — not by headcount reduction. This skill operationalizes that framing into a one-page monthly report and a quarterly content piece.
The Five ROI Dimensions (2026 DORA Report)
| Dimension | What it measures | Primary DORA metric driver |
|---|---|---|
| Cost efficiency | Rework cost avoided, incident cost reduced | Change Failure Rate ↓ |
| Productivity | Features shipped per unit time | Lead Time ↓ + Deploy Frequency ↑ |
| Developer experience | Cognitive load, on-call burden, flow state | MTTR ↓ + Deploy Frequency ↑ |
| User experience | Platform stability visible to end users | Change Failure Rate ↓ |
| Business growth | Platform velocity enabling product velocity | All four metrics → Elite |
Report Types
Type 1: Monthly one-pager (for personal tracking and dev.to longitudinal story)
5 numbers. 5 plain-language sentences. One trend line per metric. Fits on one screen.
Type 2: Quarterly LinkedIn post (public proof of platform improvement)
Hook sentence + 3 paragraphs. One chart (DORA metric trend over 3 months). Call to action.
Type 3: Annual capability review (for Dojo "proof it works" content)
Full-year metric trends mapped to the DORA tier progression (Low → Medium → High → Elite). Identifies which capabilities improved and which investments drove the improvement.
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 · 207 lines · 62 tokens per session scan A 89010785bbb9
roi-reporting is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 17d ago), licensed MIT. It adds 62 tokens to every session and 2,036 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…