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 TommyBez/evex --skill eve-agent-deliverygit clone --depth 1 https://github.com/TommyBez/evexWrote 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/tommybez/evex/eve-agent-delivery)<a href="https://agentmods.dev/skills/tommybez/evex/eve-agent-delivery"><img src="https://agentmods.dev/badge/skills/tommybez/evex/eve-agent-delivery/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/tommybez/evex/eve-agent-delivery"><img src="https://agentmods.dev/badge/skills/tommybez/evex/eve-agent-delivery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Excessive Agency · line 76 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00026 | $0.00977 |
| Opus 5 | $0.00013 | $0.00489 |
| Sonnet 5 | $0.00005 | $0.00195 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
eve-agent-delivery 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 12d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eve agent delivery
Agent-specific delivery procedure. Framework semantics live in
node_modules/eve/docs/ — load the eve skill and read the bundled docs before
using this skill. Do not restate Eve docs here.
Discovery
- Find the app root and package manager.
- Read
package.json,tsconfig.json, existingagent/files,evals/, env examples, Vercel config, and README setup notes. Done when you can list every slot the change touches. - Read
node_modules/eve/docs/README.md, then only the doc pages for those slots. Done when you have identified the guide for each slot in scope. - Identify required credentials, channel routes, webhook URLs, Vercel Connect clients, model routing, route auth, and whether deploy should be preview or production.
- Confirm local runs use a real sandbox backend. This agent uses Vercel Sandbox with Node 24 so generated Eve apps can install dependencies, build, and run evals.
- If local model-backed testing needs an AI Gateway credential and neither
AI_GATEWAY_API_KEYnorVERCEL_OIDC_TOKENis present, userun_vercel_cliactionlink_projectafter approval. - Use the Vercel MCP connection through
connection_searchfor Vercel inspection, deployment metadata, logs, Agent Runs, docs, and protected URL fetches when those tools cover the task.
Implementation
- Keep the authored surface small. Add only the files needed for the requested behavior.
- Put long operating procedures in skills so the base prompt stays readable.
- Put deterministic side effects behind tools. Use approval for external, irreversible, user-visible, or production-impacting actions.
- Keep runtime helpers in
agent/lib/; only skills and sandbox seed files reach the sandbox workspace. - Declare every environment variable in
.env.exampleor the app's existing env documentation. - Use
run_eve_clifor its supported structured, one-shot Eve operations:info,build,eval, and the file-only web channel scaffold. Usebashfor bounded local-server smoke tests. Userun_vercel_clifor Vercel Connect setup, linking, and deploys; do not route those managed operations through ordinary shell commands. - Prefer the Vercel MCP connection for read-only project/deployment/log work.
Keep Vercel CLI for local
vercel linkand Connect commands that MCP does not expose. - For channels, follow channel-setup.
What ships with it
2 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.
- 12d ago First seen · 94 lines · 26 tokens per session scan A 06bdb335199d
eve-agent-delivery is a skill published in the GitHub repository TommyBez/evex (24 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 977 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…