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 zavudev/zavu-skills --skill eve-compatgit clone --depth 1 https://github.com/zavudev/zavu-skillsWrote 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/zavudev/zavu-skills/eve-compat)<a href="https://agentmods.dev/skills/zavudev/zavu-skills/eve-compat"><img src="https://agentmods.dev/badge/skills/zavudev/zavu-skills/eve-compat/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/zavudev/zavu-skills/eve-compat"><img src="https://agentmods.dev/badge/skills/zavudev/zavu-skills/eve-compat.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.00084 | $0.00926 |
| Opus 5 | $0.00042 | $0.00463 |
| Sonnet 5 | $0.00017 | $0.00185 |
| Haiku 4.5 | $0.00008 | $0.00093 |
Grade A, and why
eve-compat 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 11d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy eve projects on Zavu
Zavu compiles an eve-layout project into a first-class Zavu agent. The user's
files are never edited: agent/instructions.md becomes the system prompt,
each agent/tools/<name>.ts becomes a tool named <name>, and Zod
inputSchema objects are converted to JSON Schema automatically.
Commands
# Import from GitHub and deploy in one step (also works for Zavu-native repos):
npx zavudev import owner/repo --sender sndr_123
npx zavudev import owner/repo#branch --root apps/agent # monorepo / branch
# Private repos: set GITHUB_TOKEN in the environment (sent only to GitHub).
# Deploy a local eve project (detected by agent/instructions.md):
cd my-eve-agent && npx zavudev deploy --sender sndr_123
The sender can come from --sender (inlined at compile time) or the
SENDER_ID function secret (npx zavudev fn secrets set SENDER_ID sndr_123).
Without either, the agent deploys but stays disconnected until a sender is
attached in the dashboard.
What maps
| eve | Zavu |
|---|---|
agent/instructions.md |
system prompt (required) |
agent/agent.ts string model |
agent model; non-string configs (provider instances, defineDynamic) fall back to the default with a warning |
agent/tools/*.ts (default-export defineTool) |
tools, named by filename stem |
Zod / JSON Schema inputSchema |
JSON Schema parameters |
package.json dependencies |
installed server-side; the eve package itself is compiled away |
What does NOT run on Zavu (always tell the user)
The deploy prints a compatibility report; these produce explicit warnings:
agent/channels/— unnecessary: Zavu senders are the channels.agent/schedules/— cron is not available on Zavu Functions yet.agent/skills/— not loaded at runtime; fold content intoinstructions.mdor a knowledge base.agent/subagents/,agent/sandbox/,agent/connections/,evals/— not supported. Agents that depend on them should run on eve's own runtime.- Tool
approvalgates andtoModelOutput— ignored per tool, with warnings. agent.tsoptionsreasoning,compaction,limits,modelOptions,outputSchema— ignored, with warnings.
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.
- 11d ago First seen · 72 lines · 84 tokens per session scan A 592700ea921b
eve-compat is a skill published in the GitHub repository zavudev/zavu-skills (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 84 tokens to every session and 926 once invoked, about $0.0004 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
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…