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 skills add thermiteau/maverick --skill mav-scope-boundariesgit clone --depth 1 https://github.com/thermiteau/maverickWrote 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/thermiteau/maverick/mav-scope-boundaries)<a href="https://agentmods.dev/skills/thermiteau/maverick/mav-scope-boundaries"><img src="https://agentmods.dev/badge/skills/thermiteau/maverick/mav-scope-boundaries/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.
<a href="https://agentmods.dev/skills/thermiteau/maverick/mav-scope-boundaries"><img src="https://agentmods.dev/badge/skills/thermiteau/maverick/mav-scope-boundaries.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00038 | $0.01641 |
| Opus 5 | $0.00019 | $0.00821 |
| Sonnet 5 | $0.00008 | $0.00328 |
| Haiku 4.5 | $0.00004 | $0.00164 |
Grade A, and why
mav-scope-boundaries 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 10d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope Boundaries
Hard limits on what Claude Code may do autonomously. These boundaries apply to all workflows, skills, and agents regardless of context.
Principle
When in doubt, don't. The cost of pausing to ask is low. The cost of an unauthorised destructive action is high.
Mechanical Enforcement
These boundaries are not prose-only. The plugin's scope-guard hook
(hooks/scope_guard.py, a PreToolUse hook) mechanically gates
destructive git operations, commits/pushes on protected branches,
infrastructure-path edits, and production-pattern commands — asking the
user in interactive sessions and denying in autonomous mode. If the hook
blocks an action you believe is authorized:
- Infrastructure: record the issue-level authorization with
uv run maverick coord authorize <repo> <issue> infra(requires themaverick-authorize-infralabel or aMaverick-Authorize: infrabody line on the issue). Never write.maverick/session-auth.jsondirectly. - Destructive git: ask the user for consent in the current session; in autonomous mode there is no consent path — do not work around the block.
- Production: there is no override, in any mode.
Do not disable the guard (MAVERICK_GUARD_DISABLE) or edit hook
configuration to get past a block — a blocked action is a signal to
escalate, not an obstacle to engineer around.
Restricted Actions
1. Infrastructure Changes
Do not modify CI/CD pipelines, deployment configs, or infrastructure-as-code unless the issue/task explicitly instructs it.
Restricted:
.github/workflows/files (GitHub Actions)Dockerfile,docker-compose.yml- Terraform, CDK, CloudFormation, Pulumi files
- Deployment scripts (
deploy.sh,release.yml) - Environment variable configuration in CI settings
- Kubernetes manifests, Helm charts
- Nginx, Apache, or reverse proxy configs
How authorisation works:
- The issue/task must explicitly request the infrastructure change
- General instructions like "set up the project" or "make it work" do not constitute authorisation
- If the issue/task says "update the CI workflow to add a lint step", that is authorisation for that specific change
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.
- 10d ago First seen · 203 lines · 38 tokens per session scan A 44121f62c707
mav-scope-boundaries is a skill published in the GitHub repository thermiteau/maverick (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,641 once invoked, about $0.0002 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
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…
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…
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…