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-testingnpx skills add evoelsewhere/evoflux --skill coding-testinggit 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.00068 | $0.00917 |
| Opus 5 | $0.00034 | $0.00458 |
| Sonnet 5 | $0.00014 | $0.00183 |
| Haiku 4.5 | $0.00007 | $0.00092 |
Grade A, and why
coding-testing 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 3d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test a code system
Build proof around failures the system must detect. Coverage percentage is a signal, not the test strategy. Do not load bundled references when this skill activates.
Define the proof obligation
- State the contract, observable outcome, boundary owner, and failure modes.
- Identify which dependencies are part of the behavior and which can be replaced without invalidating the proof.
- Map each risk to the cheapest level that can observe it: unit, component, contract, integration, end-to-end, property, load, or manual runtime check.
- Read references/test-level-selection.md when choosing between adjacent levels, testing independently deployed consumers, or replacing a flaky high-level test.
When the behavior under test has no exact declaration yet, call code_context with action="search"
once with the observable contract, error text, route, or code fragment. Use the
result to choose the symbol and test boundary; skip search when the exact symbol
is already known.
For an exact symbol under test, use code_context to identify direct
callers, references, and outbound callees that define the observable
contract or require compatibility coverage. Use impact only for a named
transitive risk and start at depth 1. Graph edges choose test boundaries; they
do not prove runtime ordering, concurrency, reflection, or environment state.
Once the proof obligation selects an exact symbol, make the graph the next
structural observation instead of continuing broad discovery.
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 result exposes ambiguity, cross-repository coverage, or another static fallback gap.
Design resilient tests
Prefer public behavior and stable seams over private calls. Make fixtures minimal, explicit, and semantically meaningful. Control time, randomness, identity, concurrency, network, filesystem, and external services at the boundary that owns them—not at every layer.
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.
- 3d ago First seen · 92 lines · 68 tokens per session scan A 0b839cac6de2
coding-testing is a skill published in the GitHub repository evoelsewhere/evoflux (5 stars, last pushed 7d ago), licensed Apache-2.0. It adds 68 tokens to every session and 917 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…
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…
issue-review
Triage a copperhead GitHub issue, attempt reproduction, and check it against the spec. Use when the user asks to review an issue, e.g. /issue-review 42 or /issue-review .