Borrowing it
Nothing to install: this file belongs to xsovad06/sova. 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/xsovad06/sova/main/.agents/skills/sova-test/SKILL.mdgit clone --depth 1 https://github.com/xsovad06/sovaWrote 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/xsovad06/sova/sova-test)<a href="https://agentmods.dev/skills/xsovad06/sova/sova-test"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/sova-test/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/xsovad06/sova/sova-test"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/sova-test.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.00019 | $0.00354 |
| Opus 5.5 | $0.00008 | $0.00142 |
| Sonnet 5.5 | $0.00004 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
sova-test 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 22d 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.
What it actually says
Test Runner
Run tests and linter, fixing issues iteratively until everything passes.
Instructions
Step 1: Identify the Scope
Determine what to test from the arguments provided when this skill is invoked or the current directory.
If unclear, check git diff --name-only to see which modules have changes.
Step 2: Run Linter
Run the project's lint command: make lint
If linter fails:
- Analyze the errors
- Fix the code issues
- Re-run until it passes
Step 3: Run Tests
Run the project's test command: make test
If tests fail:
- Analyze the test failures
- Fix the code or tests as needed
- Re-run until they pass
Step 4: Scout Check
While fixing test or lint failures, scan each touched file for pre-existing issues: flaky test patterns, stale imports, dead code. Fix them alongside the failures. Keep scout fixes small and low-risk.
Step 5: Iterate
Repeat Steps 2-4 until both linter and tests pass completely.
Cross-References
- After tests pass: Run the
sova-reviewskill to self-review before pushing - Full workflow: Use the
sova-develop-fullskill for the complete develop-test-review-pr cycle
Rules
- Always fix linter issues before running tests
- After fixing issues, re-run to verify the fix
- Continue iterating until both pass
- Report final status when everything is green
- NEVER use emojis in any output
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.
- 22d ago First seen · 57 lines · 19 tokens per session scan A 4b7f126c34cf
sova-test is a skill published in the GitHub repository xsovad06/sova (2 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 354 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-10-08.
Other skills, from other repositories
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
test-driven-development
This skill should be used when implementing features or fixing bugs. Enforces RED-GREEN-REFACTOR.
testing
This skill should be used when the user asks to "write tests", "fix failing tests", "improve test coverage" or "debug a flaky test", or reviews test quality.
pr-review
Review Cool Workflow pull requests or branch diffs. Use when Codex must inspect code changes for bugs, regressions, FreeBSD/POLA violations, missing tests, generated artifact drift, release-contract risk, or CI implications, and return findings first with file/line citations.
program-repair
Localise, write several patches, and keep the one that holds. Use when the task involves: automated program repair, fault localization, majority vote patch, repair, localize, patch generation.
bug-hunt
Reproduce, shrink, instrument, fix — then lock it with a test. Use when the task involves: bug, debug, diagnose, crash, incident, repro.