Borrowing it
Nothing to install: this file belongs to brovar/10x-pentest. 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/brovar/10x-pentest/main/.github/skills/pt-scope/SKILL.mdgit clone --depth 1 https://github.com/brovar/10x-pentestWrote 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/brovar/10x-pentest/pt-scope)<a href="https://agentmods.dev/skills/brovar/10x-pentest/pt-scope"><img src="https://agentmods.dev/badge/skills/brovar/10x-pentest/pt-scope.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.1 | $0.00093 | $0.01734 |
| Opus 5 | $0.00046 | $0.00867 |
| Sonnet 5 | $0.00019 | $0.00347 |
| Haiku 4.5 | $0.00009 | $0.00173 |
Grade A, and why
pt-scope 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 6d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pt-scope — Scope & Rules of Engagement (Stage 0)
Interactively define the engagement's scope, Rules of Engagement, and authorization, and
write context/engagements/<id>/scope.md per foundation/scope-schema.md. scope.md is the
executable definition of "never act outside scope" and of do-no-harm — a blocking input to every
later skill. This skill is a facilitator: it never invents scope, targets, or authorization; it
asks the operator and records their answers.
When to use, when to skip
- Use at engagement start, and on every retest (to re-attest authorization).
- Skip only if
scope.mdalready exists and isreadiness: ready/waivedand unchanged — then go straight to/pt-recon. Never skip re-attestation on a retest.
Initial Response
- With
<engagement-id>: proceed to Step 0. - Without: print
Usage: /pt-scope <engagement-id>. Open one first with /pt-new.and STOP.
Inputs
engagement.md— [blocking] (the identity to attach scope to; read forretest).- A seeded
scope.md— [optional]; present only on a retest — treat it as a template.
Process
Step 0: Load engagement, detect retest, resume
Read engagement.md (missing ⇒ error: engagement not found — run /pt-new. and STOP). Resume: if
scope.md already exists, load it and re-confirm/amend field-by-field — never blind-overwrite; if it
was blocked, resume at the unmet fields. If retest: true, treat any seeded scope.md as a
starting point only and require fresh authorization (new attestation + validity window) — carried
authorization is invalid (scope-schema §2).
Step 1: Discovery
Facilitate in short rounds using the host's interactive-question tool (see below). Per question:
offer 2–4 concrete options, mark one (Recommended) with a one-line tradeoff, and always include a
"Not sure / decide later" option; skip asking when the engagement intent already answers it
(confirm instead). Ask in rounds of 1–4, echo each answer back in one line, lock it. Never invent a
value; record none/unknown explicitly or capture a waiver — a blank is a gate failure. Map answers
to scope-schema fields:
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.
- 6d ago First seen · 128 lines · 0 tokens per session scan A 4a408531d7a6
pt-scope is a skill published in the GitHub repository brovar/10x-pentest (3 stars, last pushed 24d ago), licensed Apache-2.0. It adds 93 tokens to every session and 1,734 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…