Borrowing it
Nothing to install: this file belongs to c9r-io/orchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/c9r-io/orchestrator/main/.claude/skills/test-authoring/SKILL.mdgit clone --depth 1 https://github.com/c9r-io/orchestratorWrote 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/c9r-io/orchestrator/test-authoring)<a href="https://agentmods.dev/skills/c9r-io/orchestrator/test-authoring"><img src="https://agentmods.dev/badge/skills/c9r-io/orchestrator/test-authoring.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.00058 | $0.01054 |
| Opus 5 | $0.00029 | $0.00527 |
| Sonnet 5 | $0.00012 | $0.00211 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
test-authoring 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Authoring
Write tests for newly implemented functionality, or improve an existing project's test suite by using coverage data to identify gaps.
In this repository, the Rust workspace spans core/ and crates/, while the React/Vite frontend and Playwright suite live under gui/. For other targets, discover their test layout before selecting commands.
Decide Scope
Confirm which of these the user wants:
- Unit tests (backend and/or frontend)
- E2E tests (usually Playwright)
- Coverage improvement (and any target: e.g. "80%+ service layer")
If the user says "new feature implemented", treat the changed code as the test target (optimize for verifying behavior, not lines).
Discover Project Test Tooling
From repo root, identify:
- Backend language:
- Rust:
core/Cargo.tomlexists - Other: ask for the test command and coverage command
- Rust:
- Frontend:
gui/package.jsonexists (TypeScript/React frontend)
- E2E:
- Look for Playwright in
gui/playwright.config.tsandgui/package.json
- Look for Playwright in
Prefer scripts in gui/package.json and commands declared by the root Cargo workspace over inventing new ones.
Unit Tests (Backend)
Rust (core/)
Principles:
- Keep tests fast and deterministic.
- Prefer unit tests for business logic without Docker.
- Mock boundaries (repositories, HTTP clients) using traits and mock libraries (e.g.
mockall).
Placement:
- For pure logic: colocate tests in
core/src/**using#[cfg(test)] mod tests. - For API/behavior tests: use
core/tests/**if the project has a test harness there.
Workflow:
- Identify behavior added/changed (inputs, outputs, error cases).
- Add tests for:
- Happy path
- Boundary conditions
- Negative cases (validation, authz, not-found, conflict)
- Run backend tests (project-specific):
cargo test --workspace
Coverage (if requested):
- Prefer
cargo llvm-covif configured, otherwise follow the project's existing coverage commands. - If no coverage tooling exists, propose adding
cargo llvm-covsupport (do not force-install tools without user confirmation).
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 · 123 lines · 58 tokens per session scan A 3417405772a0
test-authoring is a skill published in the GitHub repository c9r-io/orchestrator (21 stars, last pushed 7d ago), licensed MIT. It adds 58 tokens to every session and 1,054 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-30.
Other skills, from other repositories
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
cw-dogfood
Use when a Codewhale change needs proving in the real product, or when asked to build/install/dogfood the local binaries: stamped release build, atomic install, fresh-shell verification, and the manual QA that gates cannot cover.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
computer-use
Full desktop control on macOS, Windows, Linux, and HarmonyOS — accessibility-first observation and actions with pixel fallback, screenshots, zoom, screen recording, and switching between registered computers as a default.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.