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 agentmods add skills/evoelsewhere/evoflux/plugin-developmentnpx skills add evoelsewhere/evoflux --skill plugin-developmentgit clone --depth 1 https://github.com/evoelsewhere/evofluxWhat 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 | $0.00102 | $0.02456 |
| Opus 5 | $0.00051 | $0.01228 |
| Sonnet 5 | $0.00020 | $0.00491 |
| Haiku 4.5 | $0.00010 | $0.00246 |
Grade A, and why
plugin-development 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 yesterday.
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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EvoFlux Plugin Development
Build portable Agent Plugins as isolated packages, then prove the package through the same lifecycle an EvoFlux user exercises. Keep the package contract portable and isolate EvoFlux-specific behavior in declared extensions.
Choose the workflow
Select the smallest path that covers the requested outcome:
- Package authoring: create or change the manifest, Skills, MCP servers, credentials, data use, tests, or archive.
- Package debugging: locate the first invalid or stale package/runtime boundary and add a regression test there.
- Platform development: change generic validation, lifecycle, runtime, API, CLI, or Plugin Center behavior without adding a domain-specific bundle.
First confirm that “plugin” means a managed Plugin Center package. EvoFlux also
has trusted in-process hooks: those are single .py files discovered from
settings.plugin_dirs() and must export async def plugin() or
class Plugin(BaseAgentHook). They are a different trust/runtime contract and
must never be scaffolded as an Agent Plugin directory. Provider plugins are
also loaded from that trusted file root by their own registry.
Hand adjacent operations to their owning workflow:
- Use
plugin-installerfor installing the legacy trusted single-file hook from a raw Python URL. - Use
skill-creatorfor a standalone skill that is not packaged in a plugin. - Use
mcp-installerfor global user/project MCP configuration outside a plugin. - For a finished package that only needs installation, use Plugin Center or the plugin CLI directly.
- Do not invent commands, agents, a storage SDK, signatures, registry import, or rich connection types; those are not current platform contracts.
Load the right contracts
Read only the references required by the work, but read each selected file completely:
- Read package-contract.md before creating or changing package structure,
plugin.json, Skills, packaging, or installation behavior. - Read runtime-and-credentials.md before implementing or debugging MCP, credentials, environment variables, data, tool grants, or runtime readiness.
- Read test-and-debug.md before testing, debugging, packing, updating, or declaring completion.
- Read evoflux-source-map.md when working inside the EvoFlux repository or when exact CLI, API, or host UI ownership matters.
What ships with it
6 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.
- yesterday First seen · 215 lines · 102 tokens per session scan A 796c42717f98
plugin-development is a skill published in the GitHub repository evoelsewhere/evoflux (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 102 tokens to every session and 2,456 once invoked, about $0.0005 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
kane-cli
Browser automation + AI test authoring via kane-cli - run browser objectives, generate & refine test scenarios/cases from a description, design requirement-linked test suites from a PRD/spec (assurance), parse NDJSON output, inspect logs, save runnable test.md. Use for any task requiring a real browser (navigate…
rove
Use when controlling Rove tasks, parallel coding attempts, hosted agent sessions, task lifecycle, or the daemon-owned issue tracker from a shell. Also the ONLY channel for messaging another agent session on this machine — rove api send, never a peer/MCP side channel.
E2E Testing Nori Skillsets Subcommands
Use when you need to interactively test a nori-skillsets CLI subcommand end-to-end via tmux, with full filesystem isolation.
release
Autonomously cut a Rove (@sma1lboy/rove) release end-to-end — detect the semver bump from pending changesets (flagging an upstream minor you didn't intend), run the release gates, bump/tag/push via scripts/release.sh, then poll the GitHub Actions Release workflow with gh until npm publish completes, diagnosing CI…
hyperframes-cli
HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, preview, play, render, publish, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, or remove-background, or when troubleshooting the…
changelog-generator
Draft Rove release notes as Changesets. Writes user-facing entries as .changeset/.md files for @sma1lboy/rove (consumed into packages/kobe/CHANGELOG.md at release time). Use when the user asks for "changelog", "release notes", "what changed", "add a changeset", or before cutting a version. Enforces Rove's no-soft-wrap…