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-discovergit 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-discover)<a href="https://agentmods.dev/skills/atournayre/claude-marketplace/auto-discover"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/auto-discover/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-discover"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/auto-discover.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.01042 |
| Opus 5 | $0.00010 | $0.00521 |
| Sonnet 5 | $0.00004 | $0.00208 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
dev:auto:discover 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 12d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration de sortie
Instructions à Exécuter
IMPORTANT : Exécute ce workflow étape par étape :
IMPORTANT : Cette commande génère un résumé de compréhension structuré et nécessite un format de sortie spécifique.
Lis le frontmatter de cette commande. Si un champ output-style est présent, exécute immédiatement :
/output-style <valeur-du-champ>
Note : Une fois que le champ output-style sera supporté nativement par Claude Code, cette instruction pourra être supprimée.
Objectif
Phase 1 du workflow automatisé : comprendre le besoin utilisateur SANS interaction.
Feature demandée (depuis Issue GitHub)
Récupérée depuis .claude/data/workflows/issue-${issue_number}-dev-workflow-state.json (Phase 0)
Titre : issue.title Description : issue.description Labels : issue.labels
Mode automatique (zéro checkpoint)
Ce skill exécute la phase 0 en mode AUTOMATIQUE :
- Pas de demande de confirmation
- Validation auto de la clarté
- FAIL si ambiguïté critique
Instructions
1. Analyser la demande
Déterminer le chemin du workflow state :
# Récupérer issue_number depuis le workflow state créé en Phase 0
# Note: si issue_number est disponible en contexte, l'utiliser directement
workflow_state_file=".claude/data/workflows/issue-${issue_number}-dev-workflow-state.json"
- Lire le workflow state
- Récupérer
issue.titleetissue.description - Évaluer la clarté et la complétude du contenu de l'issue
- Si la demande est claire → continuer
- Si la demande contient une ambiguïté critique (ex: "Ajouter auth" sans préciser OAuth/Basic/JWT)
→ FAIL immédiatement avec message explicite :
Exit code: 1❌ Description de l'issue trop ambiguë pour mode auto. Issue #123 : "Ajouter auth" Précise le contexte manquant dans l'issue GitHub : - Authentification ? (OAuth? JWT? Basic Auth?) - Intégration? (Quel service? Quel provider?) - Scope? (Utilisateurs? Admin? Tous?) Édite l'issue et relance le workflow.
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.
- 12d ago First seen · 153 lines · 19 tokens per session scan A 57338f832d4f
dev:auto:discover 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 1,042 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…