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 Koniverse/Koni-ea --skill koni-ea-opsgit clone --depth 1 https://github.com/Koniverse/Koni-eaWrote 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/koniverse/koni-ea/koni-ea-ops)<a href="https://agentmods.dev/skills/koniverse/koni-ea/koni-ea-ops"><img src="https://agentmods.dev/badge/skills/koniverse/koni-ea/koni-ea-ops.svg" alt="Measured on agentmods" 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.00152 | $0.01745 |
| Opus 5 | $0.00076 | $0.00873 |
| Sonnet 5 | $0.00030 | $0.00349 |
| Haiku 4.5 | $0.00015 | $0.00175 |
Grade A, and why
koni-ea-ops 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 8d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
koni-ea-ops — the operational lifecycle of an MQL5 EA
koni-ea-ops is the standard for organising a Koniverse MQL5 Expert Advisor as a released, deployed, tracked asset — versioning, registry & MagicNumber, deployment, release backtesting, and per-version documentation. It is the operational half; writing the EA correctly is its sibling skill [koni-ea-dev]. An EA is not "done" when it compiles — it is done when it is versioned, registered, backtested, deployed, and documented.
This standard is drawn from a live EA archive's deployment and documentation SOPs and its registry, plus the compile-service conventions behind a production MT5 terminal manager. Those sources are Koniverse-internal repositories, named in the references for provenance rather than as reading you are expected to have — everything load-bearing is restated here. It governs how EA artifacts are named, tracked, and shipped, never how their logic is written.
If you are not on the Koniverse team, two sections describe internal infrastructure you will not have: the MagicNumber workflow assumes a Notion table, and production
.ex5builds assume an internal compile service. Both have a portable equivalent stated alongside them —registry-and-magic.md§ Running your own registry anddeployment.md. The rules those tools enforce are the standard; the tools are not.
The destination is Senti, and Senti does the compiling. A release is .mq5
source pasted into Senti's Author Studio: safety scan, headless compile, Save as
EA, deploy to a linked account. Senti produces and stores the .ex5 and builds the
preset from the source's input defaults — the author never handles a binary or
writes a .set.
That is what "deploy" means throughout this skill. Sections below describing a local MetaEditor compile or an uploaded binary describe the Koniverse-internal release path, not what a partner does. Attaching an EA to a local chart is testing, never release — and doing it against an account Senti already trades doubles every position.
A working template that already follows this layout — .mq5 + .set + per-version
doc + backtest/ under <ALGO>/v<major>/v<X.YY>/ — is at
templates/mql5/STARTER_EA/.
Copy its shape rather than inventing one.
What ships with it
5 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.
- 8d ago First seen · 113 lines · 152 tokens per session scan A cbd82cd1f7c7
koni-ea-ops is a skill published in the GitHub repository Koniverse/Koni-ea (11 stars, last pushed 1mo ago), licensed MIT. It adds 152 tokens to every session and 1,745 once invoked, about $0.0008 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-30.
Other skills, from other repositories
asset-tracker-release-deploy-sop
Use when the user wants to publish a finance--tracker version end to end in one run: verify the changelog version, create or verify the GitHub release, deploy main to the server, run health checks, and push a short in-app release note with user-facing bullets.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".