Borrowing it
Nothing to install: this file belongs to Kahtaf/OpenCandle. 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/Kahtaf/OpenCandle/main/.agents/skills/test-audit/SKILL.mdgit clone --depth 1 https://github.com/Kahtaf/OpenCandleWrote 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/kahtaf/opencandle/test-audit)<a href="https://agentmods.dev/skills/kahtaf/opencandle/test-audit"><img src="https://agentmods.dev/badge/skills/kahtaf/opencandle/test-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kahtaf/opencandle/test-audit"><img src="https://agentmods.dev/badge/skills/kahtaf/opencandle/test-audit.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.01182 |
| Opus 5.5 | $0.00012 | $0.00473 |
| Sonnet 5.5 | $0.00006 | $0.00236 |
| Haiku 4.5 | $0.00003 | $0.00118 |
Grade A, and why
test-audit 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 1mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenCandle test audit
Prefer deterministic journeys through real application boundaries. Use focused unit tests for financial mathematics, parser edge cases, security decisions, and failure combinations that are expensive or difficult to reach through the UI. Optimize confidence and meaningful branch coverage, not the number of tests deleted or the percentage labeled e2e.
Inspired by OpenClaw's test-audit skill. This workflow is specific to OpenCandle; do not assume OpenClaw commands or infrastructure exist here.
Establish the baseline
- Read root and scoped
AGENTS.md,tests/AGENTS.md,vitest.config.ts,vitest.projects.ts, package scripts, and CI workflows. Check the working tree before editing. - Classify tests by what actually executes: pure unit, component integration, HTTP/storage/process integration, browser integration with simulated server responses, full application journey, or live-service canary. Directory names are insufficient.
- Record executed/passed/skipped cases and duration separately for each suite. Distinguish suites present in the repository from suites enforced by PR CI.
- Check the coverage provider is installed and the production denominator includes the requested surfaces. OpenCandle spans
src,gui/server,gui/shared,gui/web/src,gui/hosted,packages/ui/src, andworkers/provider-relay; account for TypeScript, JavaScript, and JSX. Generated files need explicit exclusions with reasons. - Report unavailable coverage honestly. Never infer percentages from file counts or passing tests. Root Vitest collection does not automatically instrument spawned CLI/server processes, browser bundles, WebContainers, or a separate relay run.
Examine candidates
Read complete candidate tests and the relevant production path. Follow callers, overlapping proof, and history before deciding. Source-text assertions, repeated inventories, self-produced expectations, and mocks that supply the claimed result are discovery signals, not automatic deletion rules.
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.
- 1mo ago First seen · 58 lines · 31 tokens per session scan A d43fba653c43
test-audit is a skill published in the GitHub repository Kahtaf/OpenCandle (28 stars, last pushed 5d ago), licensed MIT. It adds 31 tokens to every session and 1,182 once invoked, about $0.0001 per session on Opus 5.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-09-27.
Other skills, from other repositories
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
test-automation-expert
Comprehensive test automation specialist covering unit, integration, and E2E testing strategies. Expert in Jest, Vitest, Playwright, Cypress, pytest, and modern testing frameworks. Guides test pyramid design, coverage optimization, flaky test detection, and CI/CD integration. Activate on 'test strategy', 'unit tests'…
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.