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/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/generate-crud)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/generate-crud"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/generate-crud/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/thebeardedbearsas/claude-craft/generate-crud"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/generate-crud.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.00006 | $0.03059 |
| Opus 5 | $0.00003 | $0.01529 |
| Sonnet 5 | $0.00001 | $0.00612 |
| Haiku 4.5 | $0.00001 | $0.00306 |
Grade A, and why
generate-crud 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.
How it starts
The opening of the file, as written. The whole thing — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Génération CRUD Complet
Tu es un développeur Symfony senior. Tu dois générer un CRUD complet respectant la Clean Architecture, incluant Entity, Repository, Controller, Templates, Form, et Tests.
Arguments
$ARGUMENTS
Arguments :
- Nom de l'entité (ex:
Product,BlogPost) - (Optionnel) Champs au format
nom:typeséparés par des virgules
Exemple : /symfony:generate-crud Product name:string,price:decimal,description:text
MISSION
Étape 1 : Analyse des Besoins
Vérifier :
- L'entité n'existe pas déjà
- Les conventions de nommage Symfony
- La structure du projet (DDD ou standard)
Étape 2 : Génération des Fichiers
Structure à créer (Clean Architecture)
src/
├── Domain/
│ └── {Entity}/
│ ├── Entity/
│ │ └── {Entity}.php
│ ├── Repository/
│ │ └── {Entity}RepositoryInterface.php
│ └── ValueObject/
│ └── {Entity}Id.php
├── Application/
│ └── {Entity}/
│ ├── Command/
│ │ ├── Create{Entity}Command.php
│ │ ├── Update{Entity}Command.php
│ │ └── Delete{Entity}Command.php
│ ├── Handler/
│ │ ├── Create{Entity}Handler.php
│ │ ├── Update{Entity}Handler.php
│ │ └── Delete{Entity}Handler.php
│ ├── Query/
│ │ ├── Get{Entity}Query.php
│ │ └── List{Entities}Query.php
│ └── DTO/
│ └── {Entity}DTO.php
├── Infrastructure/
│ └── Persistence/
│ └── Doctrine/
│ └── {Entity}Repository.php
└── Presentation/
└── Controller/
└── {Entity}Controller.php
templates/
└── {entity}/
├── index.html.twig
├── show.html.twig
├── new.html.twig
├── edit.html.twig
└── _form.html.twig
tests/
├── Unit/
│ └── Domain/
│ └── {Entity}/
│ └── {Entity}Test.php
└── Functional/
└── Controller/
└── {Entity}ControllerTest.php
Étape 3 : Templates de Code
Entity (Domain)
<?php
declare(strict_types=1);
namespace App\Domain\{Entity}\Entity;
use App\Domain\{Entity}\ValueObject\{Entity}Id;
use Doctrine\ORM\Mapping as ORM;
#[ORM\Entity(repositoryClass: \App\Infrastructure\Persistence\Doctrine\{Entity}Repository::class)]
#[ORM\Table(name: '{entities}')]
class {Entity}
{
#[ORM\Id]
#[ORM\Column(type: 'uuid', unique: true)]
private {Entity}Id $id;
// Champs générés selon les arguments
#[ORM\Column(type: 'string', length: 255)]
private string $name;
#[ORM\Column(type: 'datetime_immutable')]
private \DateTimeImmutable $createdAt;
#[ORM\Column(type: 'datetime_immutable', nullable: true)]
private ?\DateTimeImmutable $updatedAt = null;
public function __construct({Entity}Id $id, string $name)
{
$this->id = $id;
$this->name = $name;
$this->createdAt = new \DateTimeImmutable();
}
public function getId(): {Entity}Id
{
return $this->id;
}
public function getName(): string
{
return $this->name;
}
public function setName(string $name): self
{
$this->name = $name;
$this->updatedAt = new \DateTimeImmutable();
return $this;
}
// Autres getters/setters...
}
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 · 441 lines · 6 tokens per session scan A e9a5a6facd09
generate-crud is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 7d ago), licensed MIT. It adds 6 tokens to every session and 3,059 once invoked, about $0.0000 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
migrate
Generate and manage database migrations.
flow-nexus-user-tools
User management, storage, and system utilities.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.