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 josix/agent-flow --skill evidence-driven-workgit clone --depth 1 https://github.com/josix/agent-flowWrote 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/josix/agent-flow/evidence-driven-work)<a href="https://agentmods.dev/skills/josix/agent-flow/evidence-driven-work"><img src="https://agentmods.dev/badge/skills/josix/agent-flow/evidence-driven-work/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/josix/agent-flow/evidence-driven-work"><img src="https://agentmods.dev/badge/skills/josix/agent-flow/evidence-driven-work.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.00153 | $0.02287 |
| Opus 5.5 | $0.00061 | $0.00915 |
| Sonnet 5.5 | $0.00031 | $0.00457 |
| Haiku 4.5 | $0.00015 | $0.00229 |
Grade C, and why
evidence-driven-work scanned grade C with 1 finding 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 yesterday.
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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
- Without access: name the equivalent surface, say what it would answer, and ask the user for access or give them the exact command (in a subagent, put this in your report instead). Do not work around a block or extract How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evidence-Driven Work
Base claims on what the system actually did, and communicate them so a reader understands at a glance.
Overview
These practices apply to whoever does the work, in a plain session or in any persona. They sit one level above specific tools: the tools change per domain, the habits do not.
- Inside
/orchestrate, the orchestrator's Phase 6 report follows the reporting shape in sections 7 and 8; the Intent Ledger and the<orchestration-complete>promise stay required. That report goes to the user inline: the ~3000-character report-length rule is for subagent reports, not this one. As orchestrator, hand investigation and verification to the specialists in the Delegation Decision Matrix. - Commit and PR footers: follow the user's or project's stated rule; this skill sets none.
- Boundaries: code search is exploration-strategy; gates, the Intent Ledger and environment-blocked triage are verification-gates; irreversible actions and permission blocks are agent-behavior-constraints; precedent is agentsview-usage.
Running as a subagent
Lawliet and Alphonse preload this skill, but they report to the orchestrator, not the user, and their output is parsed. So in a subagent:
- Your role's output format wins. Verdict lines (
### Verdict,### Overall:), gate lines andfile:linefindings keep their exact form and position (your agent definition puts### Verdict/### Overall:last); sections 7 and 8 shape only the prose around them. "Outcome first" doesn't apply to you: your verdict line carries the outcome, so don't move it up or add a headline restating it. - Blockers go in your report, not to the user. Wherever this skill says to ask the user, confirm a reading, or hand them a command, return it the way your role's contract says instead:
ENVIRONMENT_BLOCKEDorFAILEDwith the exact error signature for Alphonse, a finding or a note in the summary for Lawliet. The orchestrator decides whether to ask the user. - Do your own role's checks. Delegating to specialists is the orchestrator's job; you have no Agent tool, so the Delegation Decision Matrix doesn't apply to you.
- Skip what your role can't act on: change discipline (section 3) and the external-write protocol (section 8) are for whoever makes and ships the change.
What ships with it
5 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.
- yesterday First seen · 138 lines · 153 tokens per session scan C fa297cf5b4ef
evidence-driven-work is a skill published in the GitHub repository josix/agent-flow (8 stars, last pushed today), licensed MIT. It adds 153 tokens to every session and 2,287 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it C with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-25.
Other skills, from other repositories
dead-letter
Capture a failed or blocked task before it disappears. Categorizes the failure mode, extracts what was learned, and generates either a retry packet with the root cause fixed or an escalation message with specific decision points. Use whenever an agent returns a blocker, error, or partial result.
ast-grep
AST-aware structural code search and rewrite via ast-grep.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
hermes-s6-container-supervision
Modify or debug s6 services in the Hermes Docker image.
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol CLI.
module-regression
Govern cross-module regression in large repositories with a REGRESSION.md ledger that records each module's downstream consumers and executable acceptance command. After a change, run the changed module and every affected downstream command, and use observed exit codes as regression evidence under the project's…