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-performancenpx skills add evoelsewhere/evoflux --skill coding-performancegit 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.00072 | $0.00915 |
| Opus 5 | $0.00036 | $0.00458 |
| Sonnet 5 | $0.00014 | $0.00183 |
| Haiku 4.5 | $0.00007 | $0.00092 |
Grade A, and why
coding-performance 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Improve code performance
Optimize a measured bottleneck while preserving correctness and shifting no unacceptable cost elsewhere. Do not load bundled references when this skill activates.
Define the experiment
- Specify workload, data scale, concurrency, environment, warmup, cache state, user-visible metric, baseline distribution, target, and correctness invariants.
- Reproduce under representative release conditions. Separate application cost from network, dependency, background-load, and measurement noise.
- Read references/measurement-protocol.md before comparing results when samples are noisy, caching matters, tail latency is material, memory grows over time, or environments differ.
Attribute before editing
Profile the workload and identify the exact call path, query, allocation, transfer, render, lock, serialization step, or external wait that owns the material cost. A hot function is not necessarily the optimization boundary; confirm how often it runs and whether its work is avoidable.
If profiling exposes only a query label, trace name, route, allocation text, or
source fragment, call code_context with action="search" once to locate the owning declaration. Skip
search when the profiler already reports an exact declared symbol.
After profiling exposes an exact symbol, use code_context to bound its
structural context: callers for invocation sites, callees for delegated
work, and references for dispatch/registration uses. Start at depth 1 and do
not infer frequency, timing, allocation, or runtime order from static edges.
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.
Read references/code-context-contract.md only after a graph result exposes ambiguity, cross-repository traversal, or index limitations. Once profiling selects the exact symbol, make the graph the next structural observation; do not return to broad source discovery 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 · 85 lines · 72 tokens per session scan A d3f59f88b63d
coding-performance is a skill published in the GitHub repository evoelsewhere/evoflux (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 72 tokens to every session and 915 once invoked, about $0.0004 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.
general-video
The fallback workflow for authoring custom HyperFrames video compositions at any length or format — longer or multi-scene pieces, brand / sizzle reels, montages, title cards, static loops, and freeform compositions. Input- and length-agnostic. If a specialized workflow clearly fits the input — a marketed product, a…
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…