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 skills add TheBeardedBearSAS/claude-craft --skill atomic-tasksgit 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/skills/thebeardedbearsas/claude-craft/atomic-tasks)<a href="https://agentmods.dev/skills/thebeardedbearsas/claude-craft/atomic-tasks"><img src="https://agentmods.dev/badge/skills/thebeardedbearsas/claude-craft/atomic-tasks.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.01177 |
| Opus 5 | $0.00023 | $0.00589 |
| Sonnet 5 | $0.00009 | $0.00235 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
atomic-tasks 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atomic Tasks — Pattern GSD (Get Shit Done)
Pattern inspiré de gsd-build/get-shit-done (Lex Christopherson, adopté par Amazon/Google/Shopify/Webflow).
Objectif : combattre le context rot (dégradation de la qualité au-delà de ~50% de contexte utilisé) en découpant le travail en tâches atomiques exécutées dans des subagents à contexte frais.
Les 5 étapes du pattern GSD
1. Split work — Découper
Découper la feature en tâches atomiques :
- Chacune exprimable en 1-3 phrases
- Chacune réalisable en < 30 minutes
- Chacune testable indépendamment
- Chacune committable en un commit atomique
❌ MAUVAIS : "Ajouter le système d'authentification"
✅ BON :
1. "Créer la table users avec migration"
2. "Implémenter POST /auth/register avec validation email"
3. "Implémenter POST /auth/login retournant JWT"
4. "Ajouter middleware JWT verification"
5. "Tests d'intégration du flow login"
2. Small plans — Plans courts par tâche
Pour chaque tâche atomique, un plan court :
- 1 objectif
- 3-5 étapes max
- Critères de succès explicites (test qui passe, endpoint qui répond, fichier qui existe)
3. Fresh subagent contexts — Contexte neuf à chaque tâche
Règle fondamentale : chaque tâche atomique s'exécute dans un subagent à contexte frais (via Task tool ou /clear entre tâches).
| Raison | Impact |
|---|---|
| Contexte < 30% au démarrage | Qualité réponses maximale |
| Pas de résidus de la tâche précédente | Zéro confusion cross-task |
| Coût tokens optimisé | Pas de relecture inutile du contexte accumulé |
| Parallélisable | Plusieurs subagents en simultané |
Implémentation :
- Utiliser
Agenttool avecsubagent_type=general-purposeou spécialisé - Passer UNIQUEMENT le contexte nécessaire (pas tout le projet)
- Demander un rapport concis à la fin (< 200 mots)
4. Atomic git commits — Commits atomiques
Chaque tâche = 1 commit. Jamais de commit qui mélange 2 tâches.
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 · 121 lines · 47 tokens per session scan A a30f89210153
atomic-tasks is a skill published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 5d ago), licensed MIT. It adds 47 tokens to every session and 1,177 once invoked, about $0.0002 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 skills, from other repositories
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
embedded-iot
Embedded systems firmware, microcontrollers (ESP32, STM32, Arduino, Raspberry Pi), RTOS (FreeRTOS, Zephyr), IoT protocols (MQTT, CoAP, BLE), bare-metal C/C++, and hardware peripheral interfaces (I2C, SPI, UART, GPIO). Use when developing firmware, working with microcontrollers, or building IoT devices.
clean-architecture-dotnet
Use when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD patterns (invariants and events).
finding-files
Use when searching for files by name, pattern, or type in large directories, or building file lists for pipelines with other tools.