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/testing-patterns/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/testing-patterns)<a href="https://agentmods.dev/skills/xsovad06/sova/testing-patterns"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/testing-patterns/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/testing-patterns"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/testing-patterns.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.00040 | $0.01214 |
| Opus 5.5 | $0.00016 | $0.00486 |
| Sonnet 5.5 | $0.00008 | $0.00243 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
testing-patterns 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 14d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOVA Testing Patterns
When writing or modifying files in tests/, follow these conventions. Reference: docs/testing-guidelines.md.
Framework
asyncio_mode = "auto": no@pytest.mark.asyncioneeded on async tests- All tests flat in
tests/: no subdirectories, noconftest.py - Tests grouped with classes. Fixtures defined per-file, not shared.
Required Fixtures
In-memory DB (autouse in any file touching ORM):
@pytest.fixture(autouse=True)
async def setup_db(monkeypatch):
monkeypatch.setenv("SOVA_DATABASE_URL", "sqlite+aiosqlite://")
await init_db(run_migrations=False)
yield
await close_db()
Dashboard client:
@pytest.fixture
async def client(tmp_path):
app = create_app(project_dir=tmp_path)
transport = ASGITransport(app=app)
async with AsyncClient(transport=transport, base_url="http://test") as ac:
yield ac
Mock Rules
- Patch at the import site, not the definition site:
Exception: when the code under test imports inside the function body (# Correct patch("sova.adapters.github.run", new_callable=AsyncMock) # Wrong patch("sova.utils.shell.run", new_callable=AsyncMock)from x import yin the function), there is no module-level binding to patch, so patch the source module (x.y). Leave a one-line comment at the patch site so a reviewer does not "fix" it back.
1b. Environment variables: always monkeypatch.setenv/delenv, never assign to or pop from os.environ directly. A direct mutation outlives a failing test and leaks into every later test in the process.
-
Use
patch.objectfor split modules: patch the actual submodule, not the re-export facade:patch.object(agent_lifecycle, "_get_project_agents", return_value=pa) -
ShellResult factory: define per-file:
def _shell_result(stdout="", stderr="", returncode=0): return ShellResult(returncode=returncode, stdout=stdout, stderr=stderr)
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.
- 14d ago Changed · +4 lines 8d3a99fdab16
- 1mo ago Changed 0beb449491ea
- 2mo ago First seen · 89 lines · 40 tokens per session scan A 57e312b2217b
testing-patterns is a skill published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 40 tokens to every session and 1,214 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
remove-ai-slops
Removes AI-generated code smells from branch changes or an explicit file list behind regression tests. Use when the user asks to clean up, deslop, or remove AI-slop patterns from recent changes.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.
check
Auto-fix lint and formatting, then report types and tests. Run before every commit.
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…