Borrowing it
Nothing to install: this file belongs to jstoup111/ai-conductor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jstoup111/ai-conductor/main/.agents/skills/scope-check/SKILL.mdgit clone --depth 1 https://github.com/jstoup111/ai-conductorWrote 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/jstoup111/ai-conductor/scope-check)<a href="https://agentmods.dev/skills/jstoup111/ai-conductor/scope-check"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/scope-check.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium Agent Snooping · line 182 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 192 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00092 | $0.05025 |
| Opus 5 | $0.00046 | $0.02513 |
| Sonnet 5 | $0.00018 | $0.01005 |
| Haiku 4.5 | $0.00009 | $0.00502 |
Grade A, and why
scope-check 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.
How it starts
The opening of the file, as written. The whole thing — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope Check
Three scope questions recur on every change to this repository, and each has a cheap wrong answer that is expensive to unwind. Run the decision procedures below before authoring, not after.
This repository is the harness. It authors skills, agents, an engine (src/conductor), and
behavioral rules that get installed into other repositories — "consumer repositories" — which then
use the harness to build their own software. It also builds itself with itself (self-host). Those
two audiences share a checkout, which is exactly why scope errors are easy to make here and nowhere
else.
Answer A, then B, then C. B is only reached when the change adds a skill. C applies to every change.
1. Decision A — harness-repo-only, or consumer-facing?
Question: does this change serve this repository's own construction, or every repository that installs the harness?
Procedure
Walk the signals in order. The first HALT wins; a signal that does not fire is not evidence for the other side.
Step 1 — repo-only signals. Answer YES to any of these and the change is harness-repo-only:
- It touches self-host, daemon, or sandbox machinery — anything under
src/conductor/src/engine/self-host/, the live-boundary fingerprint, the isolated provider home, or a code path gated behindisSelfBuild(). That gate is the canonical shape of a repo-only feature: it isdaemon && selfHost, so every other repository's bytes are unchanged. - It touches this repository's own validation or release gates —
test/test_harness_integrity.sh,test/lint_shell.sh,test/test_provider_skill_contracts.sh,bin/generate-model-table, the release-gate classifier,.docs/release-waivers/. - It touches this repository's own CI (
.github/workflows/) or its.ai-conductor/config.ymlcustom steps. - It depends on a convention only this repository has — its
.docs/layout, its[Unreleased]changelog gate, itsVERSIONfile, its shipped-record ledger, its own branch policy.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 343 lines · 92 tokens per session scan A 6768d4f03117
scope-check is a skill published in the GitHub repository jstoup111/ai-conductor (7 stars, last pushed today), licensed Apache-2.0. It adds 92 tokens to every session and 5,025 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-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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…