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/oribarilan/97/testing-disciplinenpx skills add oribarilan/97 --skill testing-disciplinegit clone --depth 1 https://github.com/oribarilan/97Wrote 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/oribarilan/97/testing-discipline)<a href="https://agentmods.dev/skills/oribarilan/97/testing-discipline"><img src="https://agentmods.dev/badge/skills/oribarilan/97/testing-discipline.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.00032 | $0.02034 |
| Opus 5 | $0.00016 | $0.01017 |
| Sonnet 5 | $0.00006 | $0.00407 |
| Haiku 4.5 | $0.00003 | $0.00203 |
Grade A, and why
testing-discipline 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 5d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 96 lines · 32 tokens per session scan A ad4934e208a4
testing-discipline is a skill published in the GitHub repository oribarilan/97 (24 stars, last pushed 3mo ago), with no licence file. It adds 32 tokens to every session and 2,034 once invoked, about $0.0002 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
human-ai-schedule
Co-author doctrine for shared, half-hour-block daily schedules. Make sure to consult this skill whenever working in a dated daily log, journal, retro, or coordination file shared with a coworker — even if the user only says "log this at 11:00" or "what did we say last Tuesday." Default behavior of dumping procedural…
ctrl-c-v
Coding doctrine for any task that creates, modifies, or refactors code in a programming language. Make sure to consult this skill whenever the user is about to write, edit, debug, or ship code, even if they don't explicitly ask for "best practices" — Claude's default of generating new code from scratch produces code…
ctrl-c-v-tdd
Test-pattern doctrine. Tests are copyable from /.claude/patterns/tests/, three categories: input boundary, contract, effect. Make sure to consult this skill whenever code changes touch a boundary where someone else's code meets yours, even if the user doesn't say "test" or "TDD" — Claude tends to ship untested…
add-cloud-flow
Integrates Power Automate cloud flows into a Power Pages site. Lists available flows, suggests relevant ones based on intent, identifies scenarios and web roles, creates metadata files, and generates client-side code to call flows. Handles both new flow registration and adding already-registered flows to additional…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
deploy-site
Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.