Borrowing it
Nothing to install: this file belongs to hubo0520/solo-compay-os. 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/hubo0520/solo-compay-os/master/.agents/skills/qa-pytest/SKILL.mdgit clone --depth 1 https://github.com/hubo0520/solo-compay-osWrote 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/hubo0520/solo-compay-os/qa-pytest)<a href="https://agentmods.dev/skills/hubo0520/solo-compay-os/qa-pytest"><img src="https://agentmods.dev/badge/skills/hubo0520/solo-compay-os/qa-pytest/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/hubo0520/solo-compay-os/qa-pytest"><img src="https://agentmods.dev/badge/skills/hubo0520/solo-compay-os/qa-pytest.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.00028 | $0.00193 |
| Opus 5 | $0.00014 | $0.00097 |
| Sonnet 5 | $0.00006 | $0.00039 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
qa-pytest 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 10d 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
qa-pytest
Purpose
Create tests that catch regressions and prove the app runs.
Output contract (STRICT)
Return ONLY JSON:
{
"files": [
{"path": "tests/test_app.py", "content": "..."},
{"path": "pyproject.toml", "content": "..."}
],
"summary": "1-3 sentences",
"warnings": ["optional"]
}
Test requirements
- At least 1 smoke test for /healthz
- Prefer fastapi.testclient
- Keep tests deterministic and fast
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.
- 10d ago First seen · 34 lines · 28 tokens per session scan A 2f2ae66af83f
qa-pytest is a skill published in the GitHub repository hubo0520/solo-compay-os (5 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 193 once invoked, about $0.0001 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
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
testing-llm
LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.