An internal dependency checker that determines whether a project has real cloud services connected, rather than only starter placeholders or local defaults.

Use it before features that rely on cloud services, such as authentication, backups, or email, to verify those services are actually configured.

It helps prevent treating an example configuration or localhost setting as a working database, email service, or other external dependency.

_check-deps — Skill for Claude Code by flavien-ia

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 flavien-ia/hypervibe-harness --skill _check-deps

Clone the repo

git clone --depth 1 https://github.com/flavien-ia/hypervibe-harness

Made for: Claude Code.

Or install hypervibe, the plugin that ships this one along with the rest of its 87 skills, 1 hook, 1 MCP server.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/flavien-ia/hypervibe-harness/_check-deps/github.svg)](https://agentmods.dev/skills/flavien-ia/hypervibe-harness/_check-deps)

Your own site

<a href="https://agentmods.dev/skills/flavien-ia/hypervibe-harness/_check-deps"><img src="https://agentmods.dev/badge/skills/flavien-ia/hypervibe-harness/_check-deps/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/flavien-ia/hypervibe-harness/_check-deps"><img src="https://agentmods.dev/badge/skills/flavien-ia/hypervibe-harness/_check-deps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,401 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 2 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Supply Chain · line 137
Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.

Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
medium Data Exfiltration · line 130
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00082	$0.02401
Opus 5	$0.00041	$0.01201
Sonnet 5	$0.00016	$0.00480
Haiku 4.5	$0.00008	$0.00240

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

Security

Grade A, and why

_check-deps scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

1. `CLOUDFLARE_API_TOKEN` OR `CF_API_TOKEN` is present (hypervibe convention = both point to the same token - `wrangler` reads `CLOUDFLARE_API_TOKEN`, the `curl` REST API calls can use either name)

skills/_check-deps/SKILL.md · 160 lines

How it starts

The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Check Deps - Internal helper

Communication

Detect the user's language from the conversation (the user's own messages, anywhere in the session - not just this invocation: a bare slash command like /bootstrap carries no language signal by itself). If nothing in the conversation gives a signal, fall back to the OS locale (node -e "console.log(Intl.DateTimeFormat().resolvedOptions().locale)") before defaulting to English. ALWAYS reply in that language for every user-facing message: questions, progress, confirmations, summaries, errors - including any example text quoted in this skill, which is illustrative and must be translated, never sent verbatim.
Use plain, non-technical business language. Never expose internal script names (*.mjs) or jargon; describe actions in human terms.
When generating user-facing content for the scaffolded project (UI labels, emails, copy), write it in the user's language too.
Show progress as a short natural-language checklist (in-progress and done states).

Check if a project has real cloud dependencies wired up (not just T3 defaults / placeholders). Delegates to a bundled Node script - never reimplement the checks inline.

Env files read

The script merges all Next.js-style env files found at the cwd, with Next.js precedence (later overrides earlier) :

.env
.env.development
.env.development.local
.env.local

So a var set in any of these is detected - critical since some projects put DATABASE_URL in .env.local only.

Invocation

From the project root :

node "${CLAUDE_SKILL_DIR}/../../scripts/check-deps.mjs" <check1> [<check2> ...] [--include-vercel]

Output : JSON on stdout. Exit code is always 0 - parse the JSON to get per-check ok + reason.

Flag `--include-vercel`

Opt-in : runs a vercel env pull on the production environment and merges the Vercel vars on top of the local vars (Vercel wins on conflict). Useful for checks like "is production correctly configured?" (e.g., /security, /clean).

Read the full file on GitHub · 160 lines

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.

11d ago First seen · 160 lines · 82 tokens per session scan A c5bdd2d49613

Subscribe to this mod's changes

_check-deps is a skill published in the GitHub repository flavien-ia/hypervibe-harness (37 stars, last pushed yesterday), licensed Apache-2.0. It adds 82 tokens to every session and 2,401 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

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

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

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens

_check-deps