dev:auto:check-prerequisites

dev:auto:check-prerequisites is a skill for Claude Code from atournayre/claude-marketplace. It costs 24 tokens per session (562 once invoked), scanned A, original, MIT.

A prerequisite checker for the automatic development workflow.

In plain words
What is it for?
Use it to check the GitHub command-line tool, GitHub authentication, jq, Git, and required Claude Code plugins.
Why use it?
It finds missing command-line tools or authentication before development starts, instead of letting the workflow fail later.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions Claude Code.

Part of the dev plugin — 25 skills, 8 agents shipped together

Good fit Use it to check the GitHub command-line tool, GitHub authentication, jq, Git, and required Claude Code plugins.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/atournayre/claude-marketplace/auto-check-prerequisites
Install

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.

Any agent
npx skills add atournayre/claude-marketplace --skill auto-check-prerequisites
Clone the repo
git clone --depth 1 https://github.com/atournayre/claude-marketplace

Made for: Claude Code.

Or install dev, the plugin that ships this one along with the rest of its 25 skills, 8 agents.

Wrote 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.

agentmods badge for dev:auto:check-prerequisites

README.md
[![agentmods](https://agentmods.dev/badge/skills/atournayre/claude-marketplace/auto-check-prerequisites/github.svg)](https://agentmods.dev/skills/atournayre/claude-marketplace/auto-check-prerequisites)
Your own site
<a href="https://agentmods.dev/skills/atournayre/claude-marketplace/auto-check-prerequisites"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/auto-check-prerequisites/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.

agentmods 80×15 button for dev:auto:check-prerequisites

Your own site · 80×15
<a href="https://agentmods.dev/skills/atournayre/claude-marketplace/auto-check-prerequisites"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/auto-check-prerequisites.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 562 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00562
Opus 5 $0.00012 $0.00281
Sonnet 5 $0.00005 $0.00112
Haiku 4.5 $0.00002 $0.00056

Measured 12d ago against content hash d130d9b0ef7f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

dev:auto:check-prerequisites 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.

dev/skills/auto-check-prerequisites/SKILL.md · 84 lines

What it actually says

Objectif

Instructions à Exécuter

IMPORTANT : Exécute ce workflow étape par étape :

Vérifier que TOUS les prérequis système, PHP et Claude Code sont présents avant de lancer le workflow.

Exit code 1 et message d'erreur détaillé si quelque chose manque.

Instructions

1. Vérifier les outils système

# Vérifier gh CLI
if ! command -v gh &> /dev/null; then
    echo "❌ PRÉREQUIS MANQUANT : gh CLI"
    echo "Installe : https://github.com/cli/cli"
    echo "Authentifie : gh auth login"
    exit 1
fi

# Vérifier gh authentifié
if ! gh auth status &> /dev/null; then
    echo "❌ PRÉREQUIS MANQUANT : gh CLI non authentifié"
    echo "Authentifie : gh auth login"
    exit 1
fi

# Vérifier jq
if ! command -v jq &> /dev/null; then
    echo "❌ PRÉREQUIS MANQUANT : jq"
    echo "Installe : apt-get install jq (Linux) ou brew install jq (macOS)"
    exit 1
fi

# Vérifier git
if ! command -v git &> /dev/null; then
    echo "❌ PRÉREQUIS MANQUANT : git"
    exit 1
fi

2. Vérifier les plugins Claude Code

# Vérifier plugin feature-dev (optionnel pour Explore/Design, mais requis pour automation)
# Note: La vérification exacte dépend de l'API Claude Code disponible
# Pour maintenant, on va supposer qu'il est installé
# Si absent, les phases vont échouer et afficher un message clair

3. Afficher le succès

echo "✅ Tous les prérequis sont présents"
echo ""
echo "Outils vérifiés :"
echo "  ✅ gh CLI authentifiée"
echo "  ✅ jq disponible"
echo "  ✅ git disponible"
echo ""

Règles

  • Exit 1 si prérequis manquant
  • Messages d'erreur clairs avec instructions d'installation
  • Pas d'interaction : fail fast
  • Rapide : vérifications simples et directes
Changes

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.

  1. 12d ago First seen · 84 lines · 24 tokens per session scan A d130d9b0ef7f

Subscribe to this mod's changes

dev:auto:check-prerequisites is a skill published in the GitHub repository atournayre/claude-marketplace (9 stars, last pushed 6mo ago), licensed MIT. It adds 24 tokens to every session and 562 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens