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-featuregit 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-feature)<a href="https://agentmods.dev/skills/atournayre/claude-marketplace/auto-feature"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/auto-feature/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-feature"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/auto-feature.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.00018 | $0.04410 |
| Opus 5 | $0.00009 | $0.02205 |
| Sonnet 5 | $0.00004 | $0.00882 |
| Haiku 4.5 | $0.00002 | $0.00441 |
Grade A, and why
dev:auto:feature 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 11d 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 — 591 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objectif
Instructions à Exécuter
IMPORTANT : Exécute ce workflow étape par étape :
Orchestrateur du workflow de développement en 10 phases SANS interaction utilisateur.
Exécution automatique complète : récupérer issue → phases 1-8 → cleanup → créer PR. Objectif : PR créée et prête pour review, CI passe.
Issue GitHub
Issue #$ARGUMENTS (spec récupérée automatiquement)
⚠️ MODE NON-INTERACTIF
Ce workflow s'exécute automatiquement sans checkpoints utilisateur.
- Worktree OBLIGATOIRE : créé et nettoyé automatiquement
- 0 interaction requise : heuristiques appliquées à chaque décision
- CI DOIT PASSER : PHPStan niveau 9, tests
- Auto-fix en boucle : max 3 tentatives en Phase 6, puis rollback si échec
Pour un workflow interactif avec validation à chaque phase, utilise /dev:feature.
Prérequis obligatoires
Exécuter /dev:auto:check-prerequisites pour vérifier que TOUS les prérequis sont présents.
Exit code 1 et arrêt si quelque chose manque.
Workflow
Phase 0 : Vérifier les prérequis
🔄 Progression : TaskUpdate → tâche #0 en in_progress
⏱️ Démarrer le timer
Exécuter /dev:auto:check-prerequisites
Si la skill exit 1, arrêter immédiatement.
⏱️ Arrêter le timer
🔄 Progression : TaskUpdate → tâche #0 en completed
Affichage :
✅ Prérequis vérifiés
Tous les outils nécessaires sont présents :
✅ gh CLI authentifiée
✅ jq disponible
✅ git disponible
Lancement du workflow...
Phase 1 : Fetch Issue (Initialisation)
⏱️ Démarrer le timer
Déterminer le chemin :
issue_number=$ARGUMENTS
workflow_state_file=".claude/data/workflows/issue-${issue_number}-dev-workflow-state.json"
# Créer le répertoire s'il n'existe pas
mkdir -p ".claude/data/workflows"
Exécuter /dev:auto:fetch-issue $ARGUMENTS
Processus :
- Valider que l'argument est un numéro d'issue
- Récupérer l'issue GitHub via
gh issue view - Vérifier que l'issue est OPEN et a une description
- Sauvegarder les infos dans
${workflow_state_file}
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.
- 11d ago First seen · 591 lines · 18 tokens per session scan A d998f7a5a191
dev:auto:feature is a skill published in the GitHub repository atournayre/claude-marketplace (9 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 4,410 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…