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 atournayre/claude-marketplace --skill auto-codegit clone --depth 1 https://github.com/atournayre/claude-marketplaceWrote 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/atournayre/claude-marketplace/auto-code)<a href="https://agentmods.dev/skills/atournayre/claude-marketplace/auto-code"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/auto-code/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/skills/atournayre/claude-marketplace/auto-code"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/auto-code.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.00019 | $0.00535 |
| Opus 5 | $0.00010 | $0.00267 |
| Sonnet 5 | $0.00004 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
dev:auto:code 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 9d 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.
What it actually says
Objectif
Instructions à Exécuter
IMPORTANT : Exécute ce workflow étape par étape :
Phase 6 du workflow automatisé : implémenter selon le plan SANS demander d'approbation.
Démarrage immédiat de l'implémentation.
Instructions
1. Lire le contexte
Déterminer le chemin du workflow state :
# Récupérer issue_number depuis le contexte
workflow_state_file=".claude/data/workflows/issue-${issue_number}-dev-workflow-state.json"
- Lire le workflow state pour accéder au plan généré (Phase 5)
- Lire
docs/specs/{feature}.md(ou chemin du plan) - Si le plan n'existe pas, exit avec erreur
2. Implémenter selon le plan
Exécuter le contenu du plan :
- Créer les fichiers nécessaires
- Modifier les fichiers existants
- Créer les tests unitaires
Pas de checkpoint d'approbation - implémentation directe.
3. Vérification PHPStan initiale
Lancer une première vérification PHPStan sans l'arrêter l'implémentation :
vendor/bin/phpstan analyse --level=9 2>&1
Noter les résultats pour la Phase 7 (Review).
4. Mettre à jour le workflow state
{
"currentPhase": 6,
"phases": {
"6": {
"status": "completed",
"completedAt": "{ISO timestamp}",
"durationMs": {durée},
"filesCreated": ["{liste des fichiers}"],
"filesModified": ["{liste des fichiers}"],
"testsCreated": {nombre},
"phpstanErrorsInitial": {nombre}
}
}
}
Règles
- ❌ Pas de checkpoint d'approbation
- ✅ Implémenter directement selon le plan
- ✅ Créer les tests unitaires
- ✅ Vérifier PHPStan (sans bloquer)
- ❌ Ne PAS corriger les erreurs (ce sera Phase 6)
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.
- 9d ago First seen · 88 lines · 19 tokens per session scan A f8f53b5bf13c
dev:auto:code is a skill published in the GitHub repository atournayre/claude-marketplace (9 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 535 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…