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 Incept5/eve-skillpacks --skill eve-skill-distillationgit clone --depth 1 https://github.com/Incept5/eve-skillpacksWrote 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/incept5/eve-skillpacks/eve-skill-distillation)<a href="https://agentmods.dev/skills/incept5/eve-skillpacks/eve-skill-distillation"><img src="https://agentmods.dev/badge/skills/incept5/eve-skillpacks/eve-skill-distillation/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/incept5/eve-skillpacks/eve-skill-distillation"><img src="https://agentmods.dev/badge/skills/incept5/eve-skillpacks/eve-skill-distillation.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.00038 | $0.00943 |
| Opus 5 | $0.00019 | $0.00472 |
| Sonnet 5 | $0.00008 | $0.00189 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
eve-skill-distillation 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eve Skill Distillation
Use this workflow to turn repeated patterns into reusable skills.
When to distill
- A workflow has repeated across two or more jobs.
- Knowledge would benefit other agents working on the same project.
- A failure mode keeps recurring and the fix should be encoded.
Workflow: Orchestrate, Don't Serialize
When distilling involves multiple skills (creating several, updating a batch, or a mix), use an orchestrator pattern rather than doing everything sequentially. This protects your context budget and parallelizes independent work.
Step 1: Capture patterns (orchestrator)
Identify all the patterns worth distilling from recent work. For each one:
- Name the repeated steps, commands, or failure modes.
- Decide: update an existing skill, or create a new one?
- Choose the target repo/pack first - is this likely to be
./private-skills/or similar for repo-specific development workflows that are not going to be imported into other projects (private)./private-eve-dev-skills/when working in the eve-horizon repo and the skills relate to internal development of the platform itself (private)../eve-skillpacks/eve-se/for Eve platform work (deploy, auth, manifests, pipelines)../eve-skillpacks/eve-work/for general knowledge work (docs, orchestration, distillation)../eve-skillpacks/eve-design/for architecture and design thinking
Step 2: Plan work items (orchestrator)
Create a tracked work item for each skill to create or update. Each work item description must be self-contained — a worker with no prior context should be able to execute it.
Include in each work item:
- The target file path (e.g.,
eve-se/eve-auth-and-secrets/SKILL.md) - Whether this is a create or update
- The pattern being captured: what the skill should teach
- Any source material the worker should read (existing skills, reference docs, conversation history)
- The authoring rules (see "Skill Authoring Rules" below)
If there are housekeeping updates (README, ARCHITECTURE.md), add those as a final work item blocked until all skill work items complete.
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 · 83 lines · 38 tokens per session scan A 93b9dacfac3e
eve-skill-distillation is a skill published in the GitHub repository Incept5/eve-skillpacks (0 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 943 once invoked, about $0.0002 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.