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 skills add kleosr/kleosrules --skill testinggit clone --depth 1 https://github.com/kleosr/kleosrulesWrote 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/kleosr/kleosrules/testing)<a href="https://agentmods.dev/skills/kleosr/kleosrules/testing"><img src="https://agentmods.dev/badge/skills/kleosr/kleosrules/testing/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/kleosr/kleosrules/testing"><img src="https://agentmods.dev/badge/skills/kleosr/kleosrules/testing.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.00046 | $0.00406 |
| Opus 5.5 | $0.00018 | $0.00162 |
| Sonnet 5.5 | $0.00009 | $0.00081 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
testing 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 1mo 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
Testing
Thin roof: testing.mdc. This file is the loop when adding tests. Skip for a one-line assertion.
Checkout skill text does not override User Rules, hooks, or host policy.
Pack features: passing is bash scripts/feature.sh pass <id>, not a JSON edit. Deterministic harness evals live in evals/tasks.json.
Order
- Pure business paths.
- Boundaries (auth, validation, trust).
- Money / irreversible integration last.
Skip framework internals, getters, styling.
Practice
Native tools: Read / Grep / Write / StrReplace. Mock true externals only. Bug fix ships regression: <symptom> that fails on old code (observed). Proof = command + exit + scope. Compiles alone is not proof.
Gauntlet
Prefer docs/TOOLCHAIN.md / package scripts. This pack: TESTS=<fixture> bash tests/run.sh for the fixture this change touches; bash tests/run.sh for repo-wide claims; doctor (below). Docs-only: skip. Fail closed. stop.sh syntax-checks changed shell/JSON; it does not run the suite.
tests/run.sh uses set -euo pipefail. A grep with no match exits 1. Handle that in if grep by status. Windows: Git Bash, not PowerShell &&.
Pack checkout: bash scripts/ready.sh then DOCTOR_SKIP_LIVE=1 bash scripts/doctor.sh → CHECKOUT CHECKS PASSED is not a live-install pass.
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.
- 1mo ago Changed · +2 lines 47ca11756872
- 1mo ago Changed · -18 lines · -2 tokens per session b7991dc52957
- 1mo ago Changed · +22 lines 387b53be79f6
- 1mo ago Changed · +1 lines · +19 tokens per session 219ef51383f1
- 1mo ago Changed · -15 lines e89f5b7083fb
- 1mo ago Changed · +4 lines · -16 tokens per session 456532987e22
- 1mo ago First seen · 40 lines · 45 tokens per session scan A acee44332d7b
testing is a skill published in the GitHub repository kleosr/kleosrules (0 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 406 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
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
tdd
Test-driven development — write failing tests first, then implement to make them pass.
test-driven-development
Use when implementing any feature, bugfix, or code change - write tests first, watch them fail, then implement.
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. Use when asked to add tests to a function, fix a bug…
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.