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 agentmods add skills/brovar/10x-pentest/pt-code-plannpx skills add brovar/10x-pentest --skill pt-code-plangit 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-code-plan)<a href="https://agentmods.dev/skills/brovar/10x-pentest/pt-code-plan"><img src="https://agentmods.dev/badge/skills/brovar/10x-pentest/pt-code-plan.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 | $0.00112 | $0.01615 |
| Opus 5 | $0.00056 | $0.00807 |
| Sonnet 5 | $0.00022 | $0.00323 |
| Haiku 4.5 | $0.00011 | $0.00161 |
Grade A, and why
pt-code-plan 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 3d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pt-code-plan — Code Analysis Plan (Stage 3)
Turn "where the security code is" into "how we will analyse it." For each code-routed threat
objective, bind the methodology right for the repo's class + stack (web→taint/authz,
mobile→storage/platform, cloud→IaC/IAM, ai-llm→prompt-injection surfaces, …) and decompose it into
concrete, executable analysis passes (CA-NNN). Writes code/code-plan.md per
foundation/code-plan-schema.md — the runbook the agentic scanner (/pt-code-scan) executes. The
static-half analog of /pt-dynamic-plan.
When to use, when to skip
- Use after
/pt-code-map, to produce the analysis passes that drive the scan. - Skip the whole code stage if black-box (
repo_access: false) →/pt-dynamic-plan. On a re-run, amend append-only (see resume); do not regenerate over a plan the scan/review has advanced.
Initial Response
- With
<engagement-id>: proceed to Step 0. - Without: print
Usage: /pt-code-plan <engagement-id>.and STOP.
Inputs
code/review-map.md— [blocking] (theR-NNNregistry + per-repo code-derived stack + code anchors).target-profile.md— [blocking] (target_classes— the methodology keys).test-objectives.md— [blocking] (thecode/bothobjectives + priority).scope.md— [blocking] (readiness ≠ blocked;repo_access: true; authorized repos + RoE).foundation/standards/— [optional] — the Class → code-analysis methodology index.
Process
Step 0: Validate + resume
Validate scope.md (repo_access: true, else STOP → /pt-dynamic-plan), code/review-map.md (the
R-NNN registry is present), and test-objectives.md. Resume: if code/code-plan.md exists,
append new CA-NNN append-only; never reset a plan the scan/review has written (respect pass
status).
Step 1: Bind methodology per repo × class
From each repo's class + code-derived stack (review-map.md), select the technique set from
standards/ Class → code-analysis methodology. Every objective's passes cite ≥1 methodology_ref
for their class — a pass with none is a plan-time gate failure (code-plan-schema §3).
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.
- 3d ago First seen · 109 lines · 0 tokens per session scan A ba07b6b8b967
pt-code-plan is a skill published in the GitHub repository brovar/10x-pentest (2 stars, last pushed 22d ago), licensed Apache-2.0. It adds 112 tokens to every session and 1,615 once invoked, about $0.0006 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…