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/ric03uec/clawrium/tddnpx skills add ric03uec/clawrium --skill tddgit clone --depth 1 https://github.com/ric03uec/clawriumWrote 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/ric03uec/clawrium/tdd)<a href="https://agentmods.dev/skills/ric03uec/clawrium/tdd"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/tdd.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.1 | $0.00017 | $0.00412 |
| Opus 5 | $0.00009 | $0.00206 |
| Sonnet 5 | $0.00003 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
tdd 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.
What it actually says
TDD — Test-Driven Development
When the user asks you to implement, change, or fix behavior, work in the red → green → refactor loop. The loop is the discipline; do not skip a step.
The loop
- Red. Write a single failing test that names the next behavior in the smallest reasonable scope. Run the test suite (or just the new test) and confirm the failure is for the right reason (asserts on behavior, not on a missing import or typo).
- Green. Make the test pass with the minimum change. Resist the urge to refactor neighboring code, generalize, or anticipate the next test. "Minimum" means: if a literal return makes the test pass, return the literal — then write the next failing test that forces the generalization.
- Refactor. With the suite green, improve names, remove duplication, tighten interfaces. Run the suite after every refactor step. If a refactor turns the suite red, revert immediately and split it smaller.
When to break the loop
- Spike — explore an unknown API in a throwaway branch with no tests, then delete the spike and re-implement TDD-style.
- Bug report — write the failing test first that reproduces the bug, even if the production fix is one line. Without the test, the bug returns.
- Refactor-only — the suite must be green at start and end; no behavior changes in this mode.
Anti-patterns
- Writing the implementation first then back-filling tests.
- Writing many failing tests at once (you can't tell which one is driving).
- Skipping the "right reason" check in step 1.
- Refactoring while red.
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 · 41 lines · 17 tokens per session scan A 6f8310f7f0c5
tdd is a skill published in the GitHub repository ric03uec/clawrium (51 stars, last pushed 2d ago), licensed Apache-2.0. It adds 17 tokens to every session and 412 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-30.
Other skills, from other repositories
load-github-action-thread
Download retained Codex GitHub Action thread artifacts and load their rollout history into the local Codex app. Use when asked to open, load, import, resume, or inspect a Codex automation thread from a GitHub Actions run or a related GitHub issue or pull request.
uv-mapping
Inspect, generate, transform, and visualize UV channels on StaticMesh assets (UVMappingService). Use when the user asks to check/add/remove UV channels, auto-unwrap UVs, transform (tile/offset/rotate) UVs, check UV health/islands, or export a UV layout image.
depsguard
Install and run DepsGuard, a zero-dependency CLI that scans and fixes package manager configs (npm, pnpm, yarn, bun, uv) for supply chain security best practices.
python
Use when the task is Python itself, in any framework or none: PEP 695 generics, mypy --strict typing, dataclass/Protocol/TypedDict/Enum choices, asyncio.TaskGroup, stdlib idioms, src/ layout + pyproject.toml with uv, ruff+mypy+pytest gate. NOT a FastAPI/ASGI service (that is fastapi), NOT a deep pytest suite (that is…
deploying-osquery-for-endpoint-monitoring
Deploys and configures osquery for real-time endpoint monitoring using SQL-based queries to inspect running processes, open ports, installed software, and system configuration. Use when building visibility into endpoint state, threat hunting across fleet, or implementing compliance monitoring. Activates for requests…
aget-propose-actions
Propose ranked next-best actions with evidence grounding, time budgets, and execute-all default. Formalizes the fleet's highest-frequency interaction pattern.