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 agentmods add skills/mcpc-tech/dev-inspector-mcp/dev-inspectornpx skills add mcpc-tech/dev-inspector-mcp --skill dev-inspectorgit clone --depth 1 https://github.com/mcpc-tech/dev-inspector-mcpWrote 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/mcpc-tech/dev-inspector-mcp/dev-inspector)<a href="https://agentmods.dev/skills/mcpc-tech/dev-inspector-mcp/dev-inspector"><img src="https://agentmods.dev/badge/skills/mcpc-tech/dev-inspector-mcp/dev-inspector.svg" alt="Measured on agentmods" 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 | $0.00097 | $0.01978 |
| Opus 5 | $0.00048 | $0.00989 |
| Sonnet 5 | $0.00019 | $0.00396 |
| Haiku 4.5 | $0.00010 | $0.00198 |
Grade A, and why
dev-inspector 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 4d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevInspector Integration
Step 1: Analyze the User's Project
Before doing anything, determine the project setup by checking:
- Bundler -- Look for
vite.config.ts,next.config.ts,webpack.config.js, orreact-router.config.tsin the project root. - Framework -- Check
package.jsondependencies forreact,vue,svelte,solid-js,preact,next,react-router. - Package manager -- Check for
pnpm-lock.yaml(pnpm),yarn.lock(yarn), orpackage-lock.json(npm). - App Router vs Pages Router (Next.js only) -- Check if
app/layout.tsxorsrc/app/layout.tsxexists (App Router) vspages/_app.tsx(Pages Router). - Existing inspector setup -- Search for
@mcpc-tech/unplugin-dev-inspector-mcpinpackage.jsonor config files. If already configured, skip to troubleshooting.
Step 2: Install
Use the detected package manager:
# pnpm
pnpm add -D @mcpc-tech/unplugin-dev-inspector-mcp
# npm
npm i -D @mcpc-tech/unplugin-dev-inspector-mcp
# yarn
yarn add -D @mcpc-tech/unplugin-dev-inspector-mcp
Add --no-optional if the user only needs MCP (editor mode) and not ACP agents (browser mode).
Step 3: Run Automated Setup (Preferred)
The setup command auto-detects the bundler, modifies the config, and for Next.js also injects <DevInspector /> into the root layout.
npx @mcpc-tech/unplugin-dev-inspector-mcp setup
Choose flags based on the analysis from Step 1:
| Scenario | Flag |
|---|---|
| Non-HTML project (miniapps, SSR) | --entry src/main.ts |
| Next.js with non-standard layout | --entry src/app/layout.tsx |
| Cloud IDE / Docker / remote dev | --host 0.0.0.0 |
| Behind reverse proxy or tunnel | --public-base-url https://your-domain.com |
| CI or headless environment | --disable-chrome |
| Auto-open browser on start | --auto-open-browser |
| Restrict to specific agents | --visible-agents "Claude Code,Gemini CLI" |
| Preview without writing files | --dry-run |
| Specific bundler (when multiple) | --bundler vite or --bundler nextjs |
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.
- 4d ago First seen · 195 lines · 97 tokens per session scan A d628381e78c8
dev-inspector is a skill published in the GitHub repository mcpc-tech/dev-inspector-mcp (47 stars, last pushed 5mo ago), licensed MIT. It adds 97 tokens to every session and 1,978 once invoked, about $0.0005 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-30.
Other skills, from other repositories
statistical-power
Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers…
memory
Use durable BB memory when prior project knowledge or cross-project user preferences can improve the current task, and save durable new learning through the bb memory CLI.
workflows
Execute a workflow script that orchestrates multiple subagents deterministically. Use when the user explicitly requests a workflow, multi-agent orchestration, parallel or sequential agent pipelines, structured agent outputs, or a durable background workflow run.
submit-a-plugin
Submit a bb plugin to the BB Community marketplace. Use whenever a user asks to submit, list, publish, or add a plugin to the BB marketplace, or asks for a marketplace pull request. This skill validates the plugin and release, creates the marketplace entry and icon, and opens the pull request.
pr-integration-test
Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.
regex-mastery
Use this skill when writing regular expressions, debugging pattern matching,optimizing regex performance, or implementing text validation. Triggers on regex, regular expressions, pattern matching, lookahead, lookbehind, named groups, capture groups, backreferences, and any task requiring text pattern matching.