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/coding-implementationnpx skills add evoelsewhere/evoflux --skill coding-implementationgit 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.00070 | $0.01189 |
| Opus 5 | $0.00035 | $0.00594 |
| Sonnet 5 | $0.00014 | $0.00238 |
| Haiku 4.5 | $0.00007 | $0.00119 |
Grade A, and why
coding-implementation 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement a focused code change
Deliver the smallest coherent change that satisfies the observable contract. Preserve unrelated user work and avoid architecture that the requirement does not demand. A focused change is one work lane; do not create a todo unless the request contains independent deliverables.
Use the following phases in order. Leaving a phase requires its exit criterion; after leaving it, do not return to broad discovery unless a compiler, test, or runtime result names a concrete missing fact. These are efficiency boundaries, not correctness limits: when a real gap remains, name it and continue narrowly.
Phase 1 — Lock the contract and owner
In one batched model turn, inspect only applicable repository instructions, the owning source, and the nearest existing regression seam. Do not read general README, manifests, architecture, or unrelated tests unless they determine a required command or contract.
- State the changed observable behavior and the invariants that stay unchanged.
- If the owner is unknown, call
code_context(action="search")once using the stable behavior or literal. In a multi-repository workspace omit repository, path, and language filters until evidence identifies the owner. - If an exact changed symbol is known, skip search and call the smallest graph
action (
references,callers, orcallees) immediately. Useimpactonly for explicitly transitive risk and start at depth 1. - Keep repository identity. Ordinary file tools require the displayed absolute path for a non-primary repository.
- Batch independent graph queries and source reads in one model turn. Graph and
readresults already contain source and line numbers; reuse them.
Keep refresh=true for the first indexed query and after edits. Use
refresh=false only for an immediate follow-up that intentionally reuses the
same index version.
Choose the regression seam with one bounded search/read pass. Reuse the closest fixture or public API already observed. If no seam exists, create the smallest new focused test and let compiler diagnostics reveal exact missing fields; do not survey multiple unrelated test suites first.
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.
- yesterday First seen · 114 lines · 70 tokens per session scan A 84dfca27f481
coding-implementation is a skill published in the GitHub repository evoelsewhere/evoflux (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 70 tokens to every session and 1,189 once invoked, about $0.0003 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…