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/redteam)<a href="https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/redteam"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/redteam/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/redteam"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/redteam.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.00019 | $0.04012 |
| Opus 5 | $0.00010 | $0.02006 |
| Sonnet 5 | $0.00004 | $0.00802 |
| Haiku 4.5 | $0.00002 | $0.00401 |
Grade A, and why
redteam 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 9d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace Resolution
- If
$ARGUMENTSspecifies a project name, useworkspaces/$ARGUMENTS/ - Otherwise, use the most recently modified directory under
workspaces/(excludinginstructions/) - If no workspace exists, ask the user to create one first
- Read all files in
workspaces/<project>/briefs/for user context
Phase Check
- Verify
todos/active/is empty (all implemented) or note remaining items - Read
workspaces/<project>/03-user-flows/for validation criteria - Validation results go into
workspaces/<project>/04-validate/ - If gaps are found, document them and feed back to implementation (use
/implementto fix)
Execution Model
Autonomous execution model (see rules/autonomous-execution.md). Red team converges through iterative rounds. BUG and INVEST-NOW findings are fixed autonomously to convergence; INCREMENTAL-IMPROVEMENT findings are dispositioned to the deferred-quality tracking list (§ Category-Based Finding Triage below), not ground to convergence. Every dispatched reviewer still RUNS every round — the errored/empty-reviewer evidence gate (Convergence Criterion 3) is unchanged; only the DISPOSITION of findings is triaged by category, never the depth of review.
Conformance Walk is /redteam's primary standing gate — it front-loads the deterministic half (judge every unit, structural-BLOCK the irrefutable failures, hand the human the pre-computed semantic-ADVISORY worklist); it does NOT replace this adversarial round. See skills/conformance-walk/SKILL.md § "Phase-action triggers" (redteam) + § "CW vs /redteam".
Workflow
0. Posture-aware audit DEPTH — convergence is NOT posture-gated (MUST consult first)
Read .claude/learning/posture.json via state-io.js::readPosture. /redteam MUST run to convergence — every invocation at L2–L5 runs to 2 consecutive clean rounds + Convergence Criteria 4–6 below; convergence is the posture-INVARIANT target. Posture scales only the per-round DEPTH floor (WHAT each round checks), never WHETHER convergence is reached. Depth is cumulative down the ladder (skills/32-trust-posture/redteam-integration.md):
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.
- 9d ago First seen · 158 lines · 19 tokens per session scan A 8add12aef61a
redteam is a command published in the GitHub repository terrene-foundation/kailash-coc-claude-py (12 stars, last pushed 24d ago), licensed Apache-2.0. It adds 19 tokens to every session and 4,012 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-09-03.
Other commands, from other repositories
playwright-test-heal
Run all my tests and fix the failing ones.
debug
Deep-dive artifact analysis for diagnosing E2E test failures.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
fix
Correction automatisee des bugs identifies par la QA Recette.
api-aqa-flow-test-correction
Phase 7 Test Corrections of api-aqa-flow (USER APPROVAL REQUIRED).
ui-aqa-flow-test-correction
Phase 8 Test Correction of ui-aqa-flow.