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 lukedj78/dev-flow --skill eve-agentgit clone --depth 1 https://github.com/lukedj78/dev-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/lukedj78/dev-flow/eve-agent)<a href="https://agentmods.dev/skills/lukedj78/dev-flow/eve-agent"><img src="https://agentmods.dev/badge/skills/lukedj78/dev-flow/eve-agent/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/lukedj78/dev-flow/eve-agent"><img src="https://agentmods.dev/badge/skills/lukedj78/dev-flow/eve-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
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 →
- medium MCP Rug Pull · line 21 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 117 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 118 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 140 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 21 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00194 | $0.06491 |
| Opus 5.5 | $0.00078 | $0.02596 |
| Sonnet 5.5 | $0.00039 | $0.01298 |
| Haiku 4.5 | $0.00019 | $0.00649 |
Grade A, and why
eve-agent 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 22d 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
eve-agent
Scaffold and manage an eve agent — Vercel's filesystem-first agent framework, built on the open-source Workflow SDK — as the engine of a product. This skill is part of the dev-flow family and shares the same .workflow/ filesystem contract. Where dev-flow's design-md-to-app builds the Next.js app, this skill builds and grows the apps/agent (eve) that the app uses as its engine.
Before inventing a shape, read the one that exists
Thirteen reference implementations are published at https://eve.dev/templates, and
references/eve-templates.md is the need → template lookup: a multi-agent team, a station
pipeline that ends in a draft PR, an investigator that is read-only by default, a corpus-grounded
answerer, a publishing queue a human releases, the best-specified memory slot in the set. Consult it
before designing a channel, a memory slot, a multi-agent split or an approval flow from scratch.
⚠️ Read the shape, not the API. Every standalone template pins an eve older than ours — from four
minors behind to forty-four — and references/eve-docs-coverage.md records exactly what 0.71
broke in between (task() for execution: "background", taskId for agentId, the subagent.*
events gone, ctx.agent() returning a session, getSkill removed). Only the four templates inside
vercel/eve/apps/templates track eve itself, so only their call sites are current.
The one rule that matters most
Never guess the eve API. The source of truth is the bundled docs. Once eve is installed, its full documentation lives at node_modules/eve/docs/, and the live docs are at https://eve.dev/docs. Read the relevant doc there and run npx eve --help (or eve info) BEFORE scaffolding or before adding any capability. (Vercel's own official eve skill — npx skills add vercel/eve --skill eve — consists of exactly this rule and nothing else: read node_modules/eve/docs/README.md first.) eve is young and its surface can change between versions; this skill encodes the workflow and conventions, not a frozen copy of the API. If anything in this skill disagrees with the installed docs, the installed docs win.
What ships with it
15 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.
- references/ai-elements.md 17 KB
- references/contracts.md 85 KB
- references/eve-capabilities.md 56 KB
- references/eve-channels.md 14 KB
- references/eve-concepts.md 43 KB
- references/eve-conventions.md 42 KB
- references/eve-docs-coverage.md 59 KB
- references/eve-evals.md 14 KB
- references/eve-patterns.md 72 KB
- references/eve-scaffold.md 19 KB
- references/eve-templates.md 9.8 KB
- references/eve-web-integration.md 21 KB
- references/guards.template.ts 13 KB runs code
- references/staged-writes.md 11 KB
- scripts/check_eve_state.py 4.3 KB runs code
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.
- 22d ago Changed · +14 lines 0a5f44df9e4f
- 1mo ago Changed 9ce60f51a500
- 1mo ago Changed 03aed84ecec9
- 1mo ago Changed · +4 lines 3b1c921b467b
- 1mo ago Changed 0c9990f06d8a
- 1mo ago Changed · +3 lines 949646cacd79
- 1mo ago First seen · 179 lines · 194 tokens per session scan A 66606e93fe02
eve-agent is a skill published in the GitHub repository lukedj78/dev-flow (6 stars, last pushed 7d ago), licensed MIT. It adds 194 tokens to every session and 6,491 once invoked, about $0.0008 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
sdlc-regulatory
AI-driven SDLC governance framework with quality gates, risk-based autonomy caps, change traceability, Definition of Done, and a compliance crosswalk (EU AI Act, NIST AI RMF, ISO/IEC 42001, SOC 2, GDPR). Use when running or reviewing work through the BMad-style subagent SDLC, enforcing gates, classifying risk, or…
senior-bitcoin-auditor
Provides senior-level security auditing guidance for Bitcoin smart contracts including Taproot/Script, PSBT, UTXO management, Lightning Network, DLCs, and Bitcoin L2 protocols. Use when auditing Bitcoin contract code, PSBT builders, settlement engines, Lightning integrations, or ordinal/BRC-20 logic.
data-engineer
Data Engineering Lead — builds reliable, maintainable data pipelines, enforces data quality, and designs schemas that evolve safely.
archivarius
Data Organization Architect — designs and maintains well-structured, discoverable, and maintainable information architectures for codebases, documentation, and knowledge bases.
senior-solidity-auditor
Provides senior-level smart contract security auditing guidance for Solidity/EVM including vulnerability patterns, formal verification, gas optimization, and audit methodology.
senior-qa
Provides senior-level QA engineering guidance including test strategy, automation architecture, CI/CD integration, quality gates, and testing best practices for web, mobile, and API layers.