What is inspecto-onboarding?

A setup guide for installing, configuring, and diagnosing Inspecto in a code repository. It explains how to choose the local development build that should receive Inspecto.

Use it when setting up Inspecto, selecting its target build, reviewing proposed changes, applying setup patches, or completing a required IDE extension installation.

It helps avoid applying Inspecto to the wrong build when a project has several build configurations. It also guides confirmation and follow-up steps when setup is incomplete.

inspecto-onboarding — Skill for Claude Code and Codex by inspecto-dev

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 inspecto-dev/inspecto --skill inspecto-onboarding-copilot

Clone the repo

git clone --depth 1 https://github.com/inspecto-dev/inspecto

Made for: Claude Code, Codex.

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/inspecto-dev/inspecto/inspecto-onboarding-copilot.svg)](https://agentmods.dev/skills/inspecto-dev/inspecto/inspecto-onboarding-copilot)

Your own site

<a href="https://agentmods.dev/skills/inspecto-dev/inspecto/inspecto-onboarding-copilot"><img src="https://agentmods.dev/badge/skills/inspecto-dev/inspecto/inspecto-onboarding-copilot.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 583 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 91% copy Near-identical to another mod 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.00031	$0.00583
Opus 5	$0.00015	$0.00292
Sonnet 5	$0.00006	$0.00117
Haiku 4.5	$0.00003	$0.00058

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

Security

Grade A, and why

inspecto-onboarding 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 8d 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.

Origin

This is a copy

91% identical to inspecto-onboarding — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/inspecto-onboarding-copilot/SKILL.md · 35 lines

How it starts

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

Inspecto Onboarding

When the user asks GitHub Copilot to set up Inspecto:

Prefer the single-entry flow: onboard --json.
If the result returns status: "needs_target_selection", explain that this step chooses which local development build target should receive the Inspecto plugin and settings. Choose one returned target candidate and rerun with --target <candidateId>, preferring the explicit candidateId field. The CLI also accepts a returned configPath as a compatibility fallback. Do not collapse the selection back to a package path when multiple build configs exist in the same package.
If the result returns status: "needs_confirmation", summarize the proposed changes and wait for approval before rerunning with --yes.
If the result returns status: "partial_success" and diagnostics.nextSteps includes IDE extension installation, treat that as a blocking onboarding follow-up. Do not move on to dev-server validation until the extension is installed automatically or the user confirms they completed the manual install.
If the result includes handoff.patches, treat them as the primary source of truth for the remaining work. Apply those patches directly before exploring framework docs or unrelated project files.
Only do broader documentation or repo exploration when a returned patch is clearly insufficient or conflicts with the local project structure.
Use node packages/cli/bin/inspecto.js when working inside the Inspecto repository.
Otherwise prefer an already available inspecto executable before falling back to npx @inspecto-dev/cli@latest.
Use doctor --json only for explicit recovery diagnostics.

Rules:

Treat IDE extension installation as required before runtime verification.
Let the Inspecto CLI perform dependency installation and config generation.
Use the CLI's verification field as the source of truth for the dev-server step.
Default to .inspecto/settings.local.json and .inspecto/prompts.local.json.
Do not rewrite Inspecto config files manually unless the user asks for a manual fallback.
Prefer handoff.patches, handoff.pendingSteps, and handoff.assistantPrompt over ad-hoc investigation. Do not start with Next.js or Nuxt documentation searches when the CLI already returned concrete patch targets.

Read the full file on GitHub · 35 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.

8d ago First seen · 35 lines · 31 tokens per session scan A 49d7d30a12ec

Subscribe to this mod's changes

inspecto-onboarding is a skill published in the GitHub repository inspecto-dev/inspecto (23 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 583 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to inspecto-onboarding, differing in 6 lines, and is treated as a copy.

ai ai-assistant claude copilot cursor developer-tools

sdd-apply

Skill "sdd-apply" from Gentleman-Programming/gentle-ai, covering execution role, language domain contract, purpose, what you receive and execution and persistence contract.

Gentleman-Programming/gentle-ai · 0 tokens

gentle-ai-collab-perfect

Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…

Gentleman-Programming/gentle-ai · 106 tokens

inspecto-onboarding

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

Inspecto Onboarding

What this file has done since we first saw it

Other skills, from other repositories

sdd-apply

gentle-ai-collab-perfect

sdd-tasks

sdd-verify

issue-creation

sdd-spec