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 sdfdu/evopilot --skill dev-flowgit clone --depth 1 https://github.com/sdfdu/evopilotWrote 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/sdfdu/evopilot/dev-flow)<a href="https://agentmods.dev/skills/sdfdu/evopilot/dev-flow"><img src="https://agentmods.dev/badge/skills/sdfdu/evopilot/dev-flow/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/sdfdu/evopilot/dev-flow"><img src="https://agentmods.dev/badge/skills/sdfdu/evopilot/dev-flow.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.00034 | $0.00211 |
| Opus 5.5 | $0.00014 | $0.00084 |
| Sonnet 5.5 | $0.00007 | $0.00042 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
dev-flow 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 1mo 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.
What it actually says
Dev Flow
Load relevant EvoPilot context before choosing a workflow. Explicit task and repository instructions override memory.
- Inspect the smallest relevant project surface and preserve unrelated user changes.
- Make reasonable low-risk implementation decisions autonomously.
- Validate in proportion to risk: targeted checks first, broader checks when warranted.
- Use
evopilot_observeto record the workflow category and outcome, not raw source, secrets, or terminal output. - Record a preference only when explicit or supported by repeated evidence.
- On repeated failures, try safe alternatives with a bounded stopping condition; then report the actual blocker.
- Before external publication, destructive operations, credential use, or system-wide changes, call
evopilot_review_actionand require a person when directed.
Finish with the outcome, verification, and one evidence-based learning note when something durable was learned.
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.
- 1mo ago First seen · 19 lines · 34 tokens per session scan A 1986e9c9fabd
dev-flow is a skill published in the GitHub repository sdfdu/evopilot (2 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 211 once invoked, about $0.0001 per session on Opus 5.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
cvm-ai-doctor
A health-diagnosis workflow for servers, computers, virtual machines, and containers on Linux, macOS, or Windows.
nio-scan
Nio code/skill execution-risk scanner. Use when the user wants to scan a file, repo, directory, or skill for execution risks — e.g. "scan this code for risks", "is this file/plugin dangerous", "check this repo for malicious code", "run nio scan on ". Focused single-purpose skill; for other Nio operations use /nio.
nio-doctor
Nio config validator + connectivity check. Use when the user wants to validate their Nio setup — e.g. "run nio doctor", "is my nio config valid / working", "test my OAuth / external endpoint / LLM connectivity", "why isn't my scorer firing". Focused single-purpose skill; for other Nio operations use /nio.
javascript-sandbox
Best practices for using the clodex built-in JavaScript sandbox for browser debugging, fetched-data processing, attachments, and mini-app orchestration within its bundled capability boundary.
debug
Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.
Debug
Use logging calls for in-depth debugging via local log files.