A setup tool for recording which security-testing programs are available on a computer and how to run them. It stores this machine-specific information in a tool registry for later automated execution.

Use it before the first local Stage 4 execution, after changing installed tools, or when updating automatic-execution safety settings.

It removes the need to rediscover installed tools and their run methods before local security testing.

How brovar/10x-pentest configures Claude Code and Codex

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/brovar/10x-pentest/main/.github/skills/pt-tools/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/brovar/10x-pentest

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/brovar/10x-pentest/pt-tools/github.svg)](https://agentmods.dev/skills/brovar/10x-pentest/pt-tools)

Your own site

<a href="https://agentmods.dev/skills/brovar/10x-pentest/pt-tools"><img src="https://agentmods.dev/badge/skills/brovar/10x-pentest/pt-tools/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/brovar/10x-pentest/pt-tools"><img src="https://agentmods.dev/badge/skills/brovar/10x-pentest/pt-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,609 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 original No closer match found 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.00137	$0.01609
Opus 5.5	$0.00055	$0.00644
Sonnet 5.5	$0.00027	$0.00322
Haiku 4.5	$0.00014	$0.00161

Measured 1mo ago against content hash e7e5840f491a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pt-tools 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 1mo 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.

.github/skills/pt-tools/SKILL.md · 110 lines

How it starts

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

/pt-tools — Configure the Toolbench (meta)

Build/refresh context/environment/tool-registry.md — the machine-scoped capability manifest that tells /pt-dynamic-run what security tools are available on this machine and how to invoke each (local binary / Docker container / MCP server), plus a per-tool auto-exec/safety policy. Governed by foundation/tool-registry-schema.md. This is environment configuration, not methodology — it is machine-specific, git-ignored, and carries no engagement data. Idempotent: re-running refreshes availability and never discards an operator's hand-set policy without asking.

When to use, when to skip

Use once per machine before the first local execution, or to refresh after installing/removing tools, or to change the auto-exec policy.
Skip if you will run Stage-4 tools by hand — the registry is only needed for /pt-dynamic-run. Its absence is not an error; it just means local execution is unavailable and Stage 4 falls back to the human.

Initial Response

No args: proceed to Step 0 (discover + configure interactively).
--status: print the current registry (tools, backends, status, ceilings) and STOP — no changes (mirrors /pt-run --status).

Inputs

foundation/tool-catalog.md — [blocking] (the id/safety_class catalog every entry links via catalog_ref).
foundation/tool-registry-schema.md — [blocking] (the contract this skill writes to).
Existing environment/tool-registry.md — [optional] (refresh mode — merge, don't clobber operator policy).
The operator — [optional but expected] — confirms backends, images/servers, and the auto-exec policy.

Process

Step 0: Ensure the area + validate

Ensure context/environment/ exists (create with a README if absent; add it to .gitignore — the registry is machine-local). Read the schema and the catalog. If a registry exists, load it to merge.

Step 1: Discover availability per backend

For catalog tools (and any extra the operator names), probe non-destructively and record status:

local: command -v <tool> / which, then <tool> --version → bin + version.
docker: docker image ls for the expected image (ask the operator for the image ref if unknown) → docker: { image, network, evidence_mount }. Default network from default_network.
mcp: ask the operator which MCP server/function backs the tool and the arg_template mapping (MCP is a structured call, not a shell string — see schema §4).

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

1mo ago First seen · 110 lines · 0 tokens per session scan A e7e5840f491a

Subscribe to this mod's changes

pt-tools is a skill published in the GitHub repository brovar/10x-pentest (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 137 tokens to every session and 1,609 once invoked, about $0.0005 per session on Opus 5.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.

Security

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens

10x-pentest: Skill for Claude Code