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/daily-standup)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/daily-standup"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/daily-standup/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/daily-standup"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/daily-standup.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.00008 | $0.01558 |
| Opus 5 | $0.00004 | $0.00779 |
| Sonnet 5 | $0.00002 | $0.00312 |
| Haiku 4.5 | $0.00001 | $0.00156 |
Grade A, and why
daily-standup 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 10d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Génération Résumé Daily Stand-up
Tu es un assistant Scrum. Tu dois générer un résumé des activités de développement pour faciliter le daily stand-up.
Arguments
$ARGUMENTS
Arguments :
- (Optionnel) Période (défaut: depuis hier)
Exemple : /common:daily-standup ou /common:daily-standup "2024-01-15"
MISSION
Étape 1 : Collecter les Données
# Commits depuis hier
git log --since="yesterday" --oneline --all
# Branches actives
git branch -a --sort=-committerdate | head -10
# PRs ouvertes
gh pr list --state open
# Issues en cours
gh issue list --assignee @me --state open
# Fichiers modifiés localement
git status --short
Étape 2 : Générer le Résumé
══════════════════════════════════════════════════════════════
📅 DAILY STAND-UP - {YYYY-MM-DD}
══════════════════════════════════════════════════════════════
──────────────────────────────────────────────────────────────
📊 RÉSUMÉ SPRINT
──────────────────────────────────────────────────────────────
Sprint : {N}
Jour : {X}/10
Points restants : {Y}
Burndown : 📉 On track / 📈 En avance / 📊 En retard
──────────────────────────────────────────────────────────────
✅ CE QUI A ÉTÉ FAIT (HIER)
──────────────────────────────────────────────────────────────
### Commits
- {hash} {message} (@author)
- {hash} {message} (@author)
### PRs Mergées
- PR #123: {title} (@author)
### Issues Fermées
- Issue #456: {title}
──────────────────────────────────────────────────────────────
🎯 CE QUI EST PRÉVU (AUJOURD'HUI)
──────────────────────────────────────────────────────────────
### En cours
| Branche | Issue | Assigné | Status |
|---------|-------|---------|--------|
| feature/auth | #45 | @dev1 | 🟡 70% |
| fix/login | #48 | @dev2 | 🟢 90% |
### À commencer
- Issue #50: {title} (non assignée)
──────────────────────────────────────────────────────────────
🚧 BLOQUEURS / RISQUES
──────────────────────────────────────────────────────────────
| Bloqueur | Impact | Action requise |
|----------|--------|----------------|
| API externe down | PR #123 bloquée | Contacter support |
| Review en attente | PR #125 depuis 2j | @dev3 dispo ? |
──────────────────────────────────────────────────────────────
📈 PULL REQUESTS ACTIVES
──────────────────────────────────────────────────────────────
| PR | Titre | Auteur | Age | Reviews |
|----|-------|--------|-----|---------|
| #125 | Add OAuth login | @dev1 | 2j | 1/2 ✅ |
| #127 | Fix user profile | @dev2 | 1j | 0/2 ⏳ |
| #128 | Update deps | @bot | 3j | 0/1 ⏳ |
──────────────────────────────────────────────────────────────
💡 NOTES / RAPPELS
──────────────────────────────────────────────────────────────
- 🗓️ Backlog refinement demain 14h
- ⚠️ Deadline feature X : vendredi
- 📣 Sprint Review : {date}
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.
- 10d ago First seen · 217 lines · 8 tokens per session scan A 2e5a1b979d65
daily-standup is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 7d ago), licensed MIT. It adds 8 tokens to every session and 1,558 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-08-30.
Other commands, from other repositories
init-project
Initialize project with CLAUDE.md template - adaptive detection for new or existing projects.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
update-docs
Scan for recently modified files and update corresponding documentation.
handoff
Create a handoff document for seamless session continuity.
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.