Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/rakaarwaky/qwen-web-arwaky/create-test-pythonnpx skills add rakaarwaky/qwen-web-arwaky --skill create-test-pythongit clone --depth 1 https://github.com/rakaarwaky/qwen-web-arwakyWrote 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/rakaarwaky/qwen-web-arwaky/create-test-python)<a href="https://agentmods.dev/skills/rakaarwaky/qwen-web-arwaky/create-test-python"><img src="https://agentmods.dev/badge/skills/rakaarwaky/qwen-web-arwaky/create-test-python.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 | $0.00089 | $0.00828 |
| Opus 5 | $0.00044 | $0.00414 |
| Sonnet 5 | $0.00018 | $0.00166 |
| Haiku 4.5 | $0.00009 | $0.00083 |
Grade A, and why
create-test-python 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 3d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Python Test Suite
Directory Layout
modules/<name>/
├── src/
│ └── capabilities_my_class.py # NO inline tests. Clean.
├── tests/ # All test types, flat prefix naming
│ ├── contract_<module>.py
│ ├── unit_<module>_<subject>.py
│ ├── integration_<module>.py
│ ├── smoke_<app>.py
│ ├── e2e_<flow>.py
│ └── acceptance_<FRD_ID>.py
├── benches/ # Benchmark tests only
│ └── bench_<subject>.py
└── pyproject.toml
Rules
- Tests (
tests/): flat, prefix IS the virtual folder — no real subdirectories. - Benchmarks (
benches/): separate directory, usepytest-benchmark— never hand-rolled timing. - Prefix pattern:
<type>_<subject>.py - Contract tests verify class/protocol implementation exists.
- Unit tests: happy path, edge cases, error paths.
- Integration tests: use real DI container / entry point.
- E2E tests: hit real CLI/API, assert on real output.
- Acceptance tests: map 1:1 to business requirement (FRD/PRD ID).
- Smoke tests: must complete in under 5 seconds.
Test Types
| Prefix | Directory | Scope | Speed | Runs when |
|---|---|---|---|---|
contract_ |
tests/ | Protocol impl exists | ms | Every PR |
unit_ |
tests/ | One public function | ms | Every PR |
integration_ |
tests/ | Module / DI wiring | ms–s | Every PR |
smoke_ |
tests/ | App boots + responds | <5s | Every PR |
e2e_ |
tests/ | Full request lifecycle | s | Every PR (critical path) |
acceptance_ |
tests/ | Business requirement met | s | Every PR / release gate |
bench_ |
benches/ | Performance regression | s–min | Release gate / nightly |
Coverage Targets
| Layer | Minimum |
|---|---|
| Capabilities | 70% |
| Agent | 60% |
| Utility | 50% |
Workflow
- [ ] Step 1: Analyze module / app structure
- [ ] Step 2: Identify untested public API
- [ ] Step 3: Write tests/contract_<module>.py
- [ ] Step 4: Write tests/unit_<module>_<subject>.py
- [ ] Step 5: Write tests/integration_<module>.py
- [ ] Step 6: Write tests/smoke_<app>.py
- [ ] Step 7: Write tests/e2e_<flow>.py
- [ ] Step 8: Write tests/acceptance_<FRD_ID>.py
- [ ] Step 9: Write benches/bench_<subject>.py
- [ ] Step 10: Run pytest --tb=short
- [ ] Step 11: Verify coverage targets met
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.
- 3d ago First seen · 76 lines · 89 tokens per session scan A 590eea8bfc0b
create-test-python is a skill published in the GitHub repository rakaarwaky/qwen-web-arwaky (11 stars, last pushed 7d ago), licensed MIT. It adds 89 tokens to every session and 828 once invoked, about $0.0004 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
android-kotlin-testing
Android testing patterns — ViewModel unit tests with Turbine, Compose UI semantics, Hilt TestInstallIn fakes, coroutine test dispatchers, and release quality gates. Use when writing tests, setting up CI, mocking repositories, or asking "how to test ViewModel", "Compose UI test", "Turbine StateFlow".
testing-workflow
Run and debug the test suites used by php-service-template.
check-and-test
Run lint checks (ruff for Python, Biome for TS/JS), type checks (pyright for Python, tsc for TS/JS), and the standard pytest tiers (unit + e2e + tests skipped during pre-commit). Investigates failures to determine if they are application bugs or test issues, and fixes application bugs rather than weakening tests. Does…
laravel-testing
Laravel testing with PHPUnit and Dusk, feature tests, unit tests, browser tests, factories, assertions. ALWAYS activate when: writing tests, tests/Feature/, tests/Unit/, tests/Browser/, running php artisan test, test coverage, TDD. Triggers on: test failed, assertion error, factory, seeder, RefreshDatabase, actingAs…
testing-patterns
Testing patterns and principles. Unit, integration, mocking strategies.
testing
Writing or debugging tests, choosing unit vs integration style, Postgres/ClickHouse tests, regenerating ClickHouse test schema, or exporting test helpers from packages without pulling test code into production bundles.