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 commands/thebeardedbearsas/claude-craft/regressiongit clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/thebeardedbearsas/claude-craft/regression)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/regression"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/regression.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.00013 | $0.01711 |
| Opus 5 | $0.00006 | $0.00856 |
| Sonnet 5 | $0.00003 | $0.00342 |
| Haiku 4.5 | $0.00001 | $0.00171 |
Grade A, and why
regression 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 yesterday.
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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Recette Regression - Registre de Tests de Regression
Voir et gerer le registre de tests de regression. Parcourir les tests enregistres, verifier les scores de stabilite et detecter les violations de la Regle d'Or. Implemente la Regle d'Or : Un bug corrige ne doit JAMAIS reapparaitre.
Arguments
$ARGUMENTS
--list: Lister tous les tests de regression du registre--stats: Afficher le score de stabilite et l'analyse de tendance--check: Executer les tests de regression et detecter les violations--status=<status>: Filtrer par statut (active, verified, obsolete)--source=<id>: Filtrer par story/sprint source (ex: US-001)--trend: Afficher les donnees de tendance historiques--format=<type>: Format de sortie (table, yaml, json) — defaut : table
Fonctionnalites Cles
| Fonctionnalite | Description |
|---|---|
| Parcours du Registre | Lister tous les tests de regression avec metadonnees |
| Score de Stabilite | Score de 0-100 base sur le taux de reussite des tests |
| Analyse de Tendance | Tendance historique de la stabilite de regression |
| Verification Regle d'Or | Alerte sur les echecs de tests de regression |
| Filtrage par Source | Filtrer les tests par story ou sprint d'origine |
| Gestion des Statuts | Suivre les tests actifs, verifies et obsoletes |
Processus
1. Chargement du Registre
┌─────────────────────────────────────────┐
│ 1. load_registry() │
│ - Lire .recette/regression/ │
│ registry.yaml │
│ - Charger les metadonnees │
│ - Appliquer les filtres │
└─────────────────────────────────────────┘
2. Liste du Registre (--list)
┌──────────┬─────────────────────────────────┬──────────┬──────────────────────────────┬──────────┐
│ ID │ Erreur │ Source │ Chemin du Test │ Statut │
├──────────┼─────────────────────────────────┼──────────┼──────────────────────────────┼──────────┤
│ REG-001 │ Validation login non affichee │ US-001 │ tests/Unit/Auth/LoginTest.php │ verified │
│ REG-002 │ Timeout API sur /api/users │ US-001 │ tests/Func/Api/UsersTest.php │ active │
│ REG-003 │ Erreur calcul total panier │ US-015 │ tests/Unit/Cart/TotalTest.php │ active │
└──────────┴─────────────────────────────────┴──────────┴──────────────────────────────┴──────────┘
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.
- yesterday First seen · 170 lines · 13 tokens per session scan A aa896536f2d6
regression is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 1,711 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
test-suite
Run comprehensive test suite with coverage analysis.
test-e2e
Write end-to-end tests for critical user journeys.
security-scan
Run security audit on codebase.
implement
You are in full autonomous implementation mode. Follow the VisionAgent agentic task approach from CLAUDE.md rigorously.
e2e
Generate and run end-to-end tests with Playwright. Creates test journeys, runs tests, captures screenshots/videos/traces, and uploads artifacts.
checklist
Generate a custom checklist for the current feature based on user requirements.