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/xpepper/tcr-skill/tcrnpx skills add xpepper/tcr-skill --skill tcrgit clone --depth 1 https://github.com/xpepper/tcr-skillWrote 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/xpepper/tcr-skill/tcr)<a href="https://agentmods.dev/skills/xpepper/tcr-skill/tcr"><img src="https://agentmods.dev/badge/skills/xpepper/tcr-skill/tcr.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.00164 | $0.02428 |
| Opus 5 | $0.00082 | $0.01214 |
| Sonnet 5 | $0.00033 | $0.00486 |
| Haiku 4.5 | $0.00016 | $0.00243 |
Grade A, and why
tcr 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.
How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TCRDD — TCR + TDD
TCRDD = TCR (test && commit || revert) + TDD (Test Driven Development).
It blends two disciplines so that:
- You always develop the right thing (TDD's guarantee: one failing test drives each step)
- You're forced to take baby steps, because reverting wipes out wrong work fast (TCR's guarantee)
The tool that automates this workflow is git-gamble.
Run git-gamble --help for usage details.
TDD Foundation (the part TCR is built on)
TCRDD assumes you follow the Red / Green / Refactor micro-cycle from TDD:
- Red — write exactly one failing test (just enough to fail — compilation failures count)
- Green — write the minimum production code to make it pass, nothing more
- Refactor — clean up structure while keeping all tests green
Each phase maps directly to a git gamble flag. The discipline of one test at a time and minimum code to pass is what makes the gamble meaningful — if you write too much, a revert erases more than intended.
Strict TCR Rule
In strict TCR, git gamble is the test run for the current cycle.
- Do not run
cargo test,npm test, or any other standalone test command beforegit gambleinside a Red, Green, or Refactor cycle - If you already know whether the tests will pass or fail, there is no gamble
- The only acceptable test execution inside a cycle is
git gamble --red|--green|--refactor -- <test command> - Standalone test runs are allowed only outside the cycle, such as end-of-session verification or after a revert when preparing the next attempt
git gamblecommits or reverts the entire dirty worktree, not just the file you meant to touch- Start each TCR cycle from a clean worktree, or isolate unrelated edits before gambling
This is non-negotiable when the user asks for strict TCR/TCRDD.
The Three Phases
TCRDD cycles through three phases. Each phase ends in either a commit (success) or a revert (failure → retry).
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 · 227 lines · 164 tokens per session scan A 90cb309af69a
tcr is a skill published in the GitHub repository xpepper/tcr-skill (2 stars, last pushed 5mo ago), licensed MIT. It adds 164 tokens to every session and 2,428 once invoked, about $0.0008 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-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.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
nw-quality-framework
Quality gates - 11 commit readiness gates, build/test protocol, validation checkpoints, and quality metrics.
nw-mikado
Wave: CROSSWAVE Agent: Crafty (nw-software-crafter) Command: mikado.
cmux-testing
A regression test for a bug fix ships as two commits so CI proves the test catches the bug.
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.