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-init/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-init)<a href="https://agentmods.dev/skills/brovar/10x-pentest/pt-init"><img src="https://agentmods.dev/badge/skills/brovar/10x-pentest/pt-init/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/brovar/10x-pentest/pt-init"><img src="https://agentmods.dev/badge/skills/brovar/10x-pentest/pt-init.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.00087 | $0.01557 |
| Opus 5.5 | $0.00035 | $0.00623 |
| Sonnet 5.5 | $0.00017 | $0.00311 |
| Haiku 4.5 | $0.00009 | $0.00156 |
Grade A, and why
pt-init 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.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pt-init — Initialize the pentest workspace
Scaffold the context/ skeleton (engagements/, archive/, foundation/) + a README in each, and
verify the shipped foundation contracts are present. Idempotent — each artifact is
create-if-absent; re-running when everything exists only prints status and never overwrites.
When to use, when to skip
- Use to set up a fresh workspace up-front, or to check the foundation contracts are installed.
- Skip if
context/engagements/already exists and you just want to start testing — go straight to/pt-new. Re-running is harmless (a no-op), so "when in doubt, run it" is safe.
Inputs
- None — this is a scaffold; it reads no engagement artifacts.
Process
Step 1: Scaffold context/engagements/ + README.md
If the directory exists, leave it and note present; else mkdir -p and note created. If
context/engagements/README.md exists, leave it; else write:
# Engagements
In-flight security engagements. One folder per engagement at
`context/engagements/<engagement-id>/`, identified by an `engagement.md` identity file
(see `foundation/engagement-schema.md`). Created via `/pt-new`. Holds the staged artifacts:
scope, target profile + attack surface, threat model + test-objectives ledger, code review,
dynamic testing + evidence, one file per finding, and the final report. Archive with
`/pt-archive` once the report is signed off.
Step 2: Scaffold context/archive/ + README.md
Directory: create-if-absent. README-if-absent:
# Archive
Sealed engagements, moved here from `context/engagements/` by `/pt-archive` once the report is
signed off. Read-only by convention; skills refuse to write here.
Step 3: Scaffold context/foundation/ + README.md, then verify the contract set
Directory: create-if-absent. README-if-absent:
# Foundation
Durable methodology truth, reusable across every engagement — owned by the methodology, not by any
one engagement. Edit-in-place; supersede via `foundation/archive/YYYY-MM-DD-<doc>.md`.
- **Schema contracts (locked):** `engagement-schema.md`, `scope-schema.md`,
`target-profile-schema.md`, `test-objectives-schema.md`, `finding-schema.md`,
`dynamic-test-plan-schema.md`, `report-template.md`, `tool-registry-schema.md`. Every skill validates
its `[blocking]` inputs against these before running (validate-at-seams).
- **Reference libraries:** `methodology.md`, `tool-catalog.md`, `threat-library.md`, `standards/`.
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 · 142 lines · 0 tokens per session scan A d97ba417a356
pt-init is a skill published in the GitHub repository brovar/10x-pentest (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 87 tokens to every session and 1,557 once invoked, about $0.0003 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.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…