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 msinclair25/mdevolved --skill owd-evegit clone --depth 1 https://github.com/msinclair25/mdevolvedWrote 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/msinclair25/mdevolved/owd-eve)<a href="https://agentmods.dev/skills/msinclair25/mdevolved/owd-eve"><img src="https://agentmods.dev/badge/skills/msinclair25/mdevolved/owd-eve/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/msinclair25/mdevolved/owd-eve"><img src="https://agentmods.dev/badge/skills/msinclair25/mdevolved/owd-eve.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.00090 | $0.01408 |
| Opus 5.5 | $0.00036 | $0.00563 |
| Sonnet 5.5 | $0.00018 | $0.00282 |
| Haiku 4.5 | $0.00009 | $0.00141 |
Grade A, and why
owd-eve 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 23d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MDevolved + Eve
Legacy compatibility path. New setups should use
mdevolved-eve; keep this pack for existingowdconnections and receipts.
Keep one universal MDevolved server. Apply this profile as Eve-side configuration and instructions; never change MCP framing, OAuth, tool schemas, or MDevolved authority for Eve.
Confirm the runtime
- Confirm the repository uses Eve and has an
agent/directory. - Read the repository's
AGENTS.mdand local agent instructions. - Add
agent/connections/owd.ts; its filename makes the Eve connection nameowd. - Use
defineMcpClientConnectionwith the deployment's standard remote Streamable HTTP/mcpURL. - Use
connect()from@vercel/connect/evewithprincipalType: "user",autoProvision: true, the MDevolved MCP URL as the token resource, and only these source-grant scopes:vault.read,project.initialize.request, andproject.connect.request.
Do not add a proxy, static bearer token, app principal, custom tool schema, client-side Project authority, or a second MDevolved endpoint. Do not pin a local tool allowlist: MDevolved's advertised catalog and server-side grant remain authoritative.
Eve 0.65.0 can install integrations from its registry with eve add or
interactive /add. MDevolved is not represented as registry-installed until Eve's
upstream registry accepts it. Until then, use the generated
agent/connections/owd.ts module from the MDevolved dashboard; do not claim that
eve add owd is available.
Authenticate in the right context
Eve's user-scoped connection requires a signed-in user route. Let Eve pause the tool call, open its connection flow, and resume after the owner approves the exact MDevolved vault and folder boundary. Credentials stay in Vercel Connect rather than model-visible history.
If Eve reports principal_required, use a user-authenticated Eve route. This
is not an MDevolved revocation and is not repaired by reconnecting MDevolved or changing to
principalType: "app".
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.
- 23d ago Changed 847187565ad2
- 26d ago Changed 9461a8e091eb
- 1mo ago Changed efacd3bcfbb4
- 1mo ago First seen · 128 lines · 90 tokens per session scan A 234b68f36dd9
owd-eve is a skill published in the GitHub repository msinclair25/mdevolved (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 90 tokens to every session and 1,408 once invoked, about $0.0004 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-09-01.
Other skills, from other repositories
triage-tasks
Use when you want to review and batch-update open vault task statuses for the current project or across all projects.
tackle-task
Use when starting work on a specific vault task, when a task title or path is mentioned, or when coming from triage output.
add-task
Use when you want to quickly capture a new task in the vault from a title, with optional priority and due date.
ariadne:workstream-tracking
Create, audit, or improve Obsidian Kanban work boards and Dataview dashboards for durable project, roadmap, evaluation, implementation, QA, or recurring workstream tracking inside an agent-maintained vault.
project-flow-ops
Use when projects or tasks need explicit state, WIP control, ownership, definitions of done, blocker handling, and verified closure.
pkm-session-end
Use when wrapping up a work session — creates devlog entry, captures undocumented decisions/research/debugging, audits link health of session work, and updates project index. Primarily used via the pkm-capture agent.