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.
git clone --depth 1 https://github.com/terrene-foundation/kailash-coc-claude-pyWrote 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/commands/terrene-foundation/kailash-coc-claude-py/test)<a href="https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/test"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/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/commands/terrene-foundation/kailash-coc-claude-py/test"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/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.00000 | $0.00810 |
| Opus 5 | $0.00000 | $0.00405 |
| Sonnet 5 | $0.00000 | $0.00162 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- test — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/test - Testing Strategies Quick Reference
Purpose
Load the testing strategies skill for 3-tier testing with NO MOCKING policy enforcement in Tier 2-3.
Step 0: Detect Project Testing Stack
Before loading test patterns, check what the project uses:
- Look at
requirements.txt,pyproject.toml,setup.pyforpytest,unittest - Look at
package.jsonforjest,vitest,mocha,playwright - Look at
pubspec.yamlforflutter_test,integration_test - Look for existing test directories (
tests/,test/,__tests__/,spec/)
Adapt examples to the project's testing framework. The 3-tier strategy and NO MOCKING policy apply universally regardless of framework.
Quick Reference
| Command | Action |
|---|---|
/test |
Load testing patterns and tier strategy |
/test tier1 |
Show unit test patterns (mocking allowed) |
/test tier2 |
Show integration test patterns (NO MOCKING) |
/test tier3 |
Show E2E test patterns (NO MOCKING) |
What You Get
- 3-tier testing strategy
- NO MOCKING enforcement (Tier 2-3)
- Real infrastructure patterns
- Coverage requirements
3-Tier Strategy
| Tier | Type | Mocking | Focus |
|---|---|---|---|
| Tier 1 | Unit Tests | ALLOWED | Isolated functions |
| Tier 2 | Integration | PROHIBITED | Component interactions |
| Tier 3 | E2E | PROHIBITED | Full user journeys |
Quick Pattern
# Tier 2: Real database (example with pytest)
@pytest.fixture
def db():
"""Use real infrastructure, not mocks."""
conn = sqlite3.connect(":memory:")
yield conn
conn.close()
def test_user_creation(db):
# NO MOCKING - real database operations
db.execute("INSERT INTO users (name) VALUES (?)", ("test",))
result = db.execute("SELECT * FROM users WHERE name = ?", ("test",)).fetchone()
assert result is not None
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.
- 6d ago First seen · 111 lines · 0 tokens per session scan A d2ade2e31d6d
test is a command published in the GitHub repository terrene-foundation/kailash-coc-claude-py (12 stars, last pushed 21d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 810 tokens. 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-03.
Other commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
gsd:add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
testing
Comprehensive testing through distributed execution.
verify
You are invoking the verify skill - comprehensive verification following Boris Cherny's pattern.
test
Escrever e rodar testes (skill 05 — QA Engineer).
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.