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/optimize-doctrine)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/optimize-doctrine"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/optimize-doctrine.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.00006 | $0.02069 |
| Opus 5 | $0.00003 | $0.01035 |
| Sonnet 5 | $0.00001 | $0.00414 |
| Haiku 4.5 | $0.00001 | $0.00207 |
Grade A, and why
optimize-doctrine 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 4d 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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimisation Requêtes Doctrine
Tu es un expert Doctrine et DBA. Tu dois analyser les requêtes Doctrine du projet, identifier les problèmes de performance (N+1, index manquants, requêtes lentes) et proposer des optimisations.
Arguments
$ARGUMENTS
Arguments :
- (Optionnel) Chemin vers une entité ou repository spécifique
Exemple : /symfony:optimize-doctrine ou /symfony:optimize-doctrine src/Entity/Order.php
MISSION
Étape 1 : Activer le Profiling
# config/packages/dev/doctrine.yaml
doctrine:
dbal:
profiling_collect_backtrace: true
when@dev:
doctrine:
dbal:
logging: true
Étape 2 : Identifier les Problèmes
Détecter les N+1 Queries
// PROBLÈME: N+1
$orders = $orderRepository->findAll();
foreach ($orders as $order) {
echo $order->getCustomer()->getName(); // 1 requête par order!
}
// SOLUTION: Eager Loading
$orders = $orderRepository->createQueryBuilder('o')
->leftJoin('o.customer', 'c')
->addSelect('c')
->getQuery()
->getResult();
Analyser avec le Debug Toolbar
# Vérifier le nombre de requêtes
docker compose exec php php bin/console doctrine:query:sql "SELECT 1"
# Profiler
docker compose exec php php bin/console debug:container doctrine.dbal.default_connection
Étape 3 : Optimisations Courantes
3.1 Lazy Loading → Eager Loading
// Repository
class OrderRepository extends ServiceEntityRepository
{
public function findWithRelations(): array
{
return $this->createQueryBuilder('o')
->leftJoin('o.customer', 'c')->addSelect('c')
->leftJoin('o.items', 'i')->addSelect('i')
->leftJoin('i.product', 'p')->addSelect('p')
->orderBy('o.createdAt', 'DESC')
->getQuery()
->getResult();
}
}
3.2 Partial Selects (réduire les données)
// Ne récupérer que les champs nécessaires
$results = $this->createQueryBuilder('u')
->select('partial u.{id, email, name}')
->getQuery()
->getResult();
// Ou utiliser un DTO
$results = $this->createQueryBuilder('u')
->select('NEW App\DTO\UserListDTO(u.id, u.email, u.name)')
->getQuery()
->getResult();
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.
- 4d ago First seen · 328 lines · 6 tokens per session scan A 7a0ded4b451f
optimize-doctrine is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 5d ago), licensed MIT. It adds 6 tokens to every session and 2,069 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.
help
Explain Ralph Wiggum technique and available commands.
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.