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 evoelsewhere/evoflux --skill plugin-developmentgit clone --depth 1 https://github.com/evoelsewhere/evofluxWrote 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/evoelsewhere/evoflux/plugin-development)<a href="https://agentmods.dev/skills/evoelsewhere/evoflux/plugin-development"><img src="https://agentmods.dev/badge/skills/evoelsewhere/evoflux/plugin-development/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/evoelsewhere/evoflux/plugin-development"><img src="https://agentmods.dev/badge/skills/evoelsewhere/evoflux/plugin-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Agent Snooping · line 109 Skill accesses MCP server configuration files (mcp.json). MCP configs contain server URLs, authentication tokens, and tool definitions — reading them allows the skill to discover and potentially abuse other tool integrations.Fix: Remove all code or instructions that read MCP configuration files (mcp.json). MCP server details should be managed by the agent runtime, not read by individual skills.
- medium Excessive Agency · line 105 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.00115 | $0.02706 |
| Opus 5.5 | $0.00046 | $0.01082 |
| Sonnet 5.5 | $0.00023 | $0.00541 |
| Haiku 4.5 | $0.00012 | $0.00271 |
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 17d 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 — 217 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 the
plugins/ subdirectory of the EvoFlux configuration directory (or the
directories listed in EVOFLUX_PLUGINS_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:
- Installing a trusted single-file hook from a raw Python URL: read the
plugin-installerskill. - A standalone skill that is not packaged in a plugin: read the
skill-creatorskill. - Global user/project MCP configuration outside a plugin: read the
mcp-installerskill. - 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; none of those is part of the platform contract.
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 changing the Plugin Platform inside the EvoFlux repository or when exact CLI, API, or host UI ownership matters.
What ships with it
4 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.
- 17d ago Changed 9ca6f8405689
- 22d ago Changed · +2 lines · +13 tokens per session f57d8eecae20
- 1mo ago First seen · 215 lines · 102 tokens per session scan A 796c42717f98
plugin-development is a skill published in the GitHub repository evoelsewhere/evoflux (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 115 tokens to every session and 2,706 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
review-diff
Review the working-tree diff for bugs and over-engineering.
openai-docs
Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, latest/current/default-model prompting guidance, or model upgrade and prompt-upgrade guidance; use…
3D模型与视频特效
A tool for generating 3D models from text or images and applying preset animated effects to pictures. It does not generate ordinary images or full videos.
tencent-docs-sheet-generation
A tool for creating a new Excel workbook (.xlsx) from written requirements or reference PDF, Word, or presentation files. It is for starting without an existing spreadsheet file.
html-to-docx
A converter that turns HTML into an editable Microsoft Word document (.docx). It maps common HTML structure and styles, and can include images, tables, a table of contents, headers, and footers.
Presentations
Read, create or edit PowerPoint or Google Slides decks. Use for presentation, slide deck, PowerPoint, PPT, PPTX, or Google Slides requests.