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 exploregit 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/explore)<a href="https://agentmods.dev/skills/atournayre/claude-marketplace/explore"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/explore/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/explore"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/explore.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.01168 |
| Opus 5 | $0.00009 | $0.00584 |
| Sonnet 5 | $0.00004 | $0.00234 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
dev:explore 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration de sortie
IMPORTANT : Cette skill génère un résumé d'exploration structuré et nécessite un format de sortie spécifique.
Lis le frontmatter de cette skill. 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.
Output-style requis : bullet-points
Objectif
Instructions à Exécuter
IMPORTANT : Exécute ce workflow étape par étape :
Phase 1 du workflow de développement : explorer le codebase pour comprendre les patterns existants.
Prérequis
⚠️ Plugin feature-dev requis pour les agents code-explorer.
Si non installé :
/plugin install feature-dev@claude-code-plugins
Instructions
1. Lire le contexte
- Lire
.claude/data/.dev-workflow-state.jsonpour connaître la feature en cours - Si le fichier n'existe pas, demander à l'utilisateur de lancer
/dev:discoverd'abord
2. Créer les tâches d'exploration
Utiliser TaskCreate pour chaque agent :
TaskCreate #1: Explorer features similaires (code-explorer)
TaskCreate #2: Mapper architecture et abstractions (code-explorer)
TaskCreate #3: Analyser intégrations (code-explorer) - optionnel
TaskCreate #4: Consolider résultats et présenter résumé
Important :
- Utiliser
activeForm(ex: "Explorant features similaires", "Mappant l'architecture") - Tâche #3 optionnelle selon pertinence de la feature
- Tâche #4 bloquée par les agents 1-3 (utiliser
addBlockedBy) - Les agents 1-3 se lancent en parallèle
3. Lancer les agents code-explorer
⚠️ Avant de lancer les agents : Marquer les tâches en in_progress :
TaskUpdate→ tâche #1 enin_progressTaskUpdate→ tâche #2 enin_progressTaskUpdate→ tâche #3 enin_progress(si créée)
Lancer 2-3 agents code-explorer en parallèle avec des focus différents :
Agent 1 : Features similaires
Trouve des features similaires à "{feature}" dans le codebase.
Trace leur implémentation de bout en bout.
Retourne les 5-10 fichiers clés à lire.
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 · 154 lines · 18 tokens per session scan A a824561afab2
dev:explore 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 1,168 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…