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-run/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-run)<a href="https://agentmods.dev/skills/brovar/10x-pentest/pt-run"><img src="https://agentmods.dev/badge/skills/brovar/10x-pentest/pt-run/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-run"><img src="https://agentmods.dev/badge/skills/brovar/10x-pentest/pt-run.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.00086 | $0.01375 |
| Opus 5 | $0.00043 | $0.00687 |
| Sonnet 5 | $0.00017 | $0.00275 |
| Haiku 4.5 | $0.00009 | $0.00137 |
Grade A, and why
pt-run 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 8d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pt-run — Engagement Conductor (meta)
Re-derive an engagement's current stage from on-disk artifacts and print the next handoff — the
"where am I / what's next" helper. The human triggers each stage; pt-run just tells them which stage
that is. It never does a stage's work. --status prints the stage table without routing. (Analog of
10x-test-plan's state machine.)
When to use, when to skip
- Use to resume an engagement, or to check progress (
--status), without remembering where you left off. - Skip if you already know the next step — just run that skill directly.
Initial Response
- With
<engagement-id>(optionally--status): proceed to Step 0. - Without: print
Usage: /pt-run <engagement-id> [--status].and STOP.
Inputs
- The engagement folder — [blocking] (reads whatever staged artifacts exist; derives state from them).
Process
Step 0: Load + derive state (never from memory — from files)
Read engagement.md. Then derive the current stage from which artifacts exist and their gate state,
in order:
| On-disk state | Current stage → next |
|---|---|
no scope.md (or readiness: blocked) |
→ /pt-scope |
scope ready, no target-profile.md/attack-surface.md |
→ /pt-recon |
profile+surface, no test-objectives.md |
→ /pt-threat-model |
register done, repo_access true, code stage incomplete |
→ /pt-code-map → /pt-code-plan → /pt-code-scan → /pt-code-review |
register done, repo_access false OR code stage complete, no dynamic/test-plan.md |
→ /pt-dynamic-plan |
runbook has planned cases without evidence |
→ HUMAN runs them or /pt-dynamic-run (if environment/tool-registry.md exists), then /pt-dynamic-analyze |
evidence present / dynamic objectives not all terminal |
→ /pt-dynamic-analyze |
all dynamic/both terminal, no review/findings-review.md (or fail) |
→ /pt-pentest-review |
review pass/waived, no report/final-report.md |
→ /pt-report |
report present, engagement.md not closed |
→ /pt-archive |
closed |
done (offer /pt-new --from <id> for a retest) |
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.
- 8d ago First seen · 104 lines · 0 tokens per session scan A 3587620a3fef
pt-run is a skill published in the GitHub repository brovar/10x-pentest (3 stars, last pushed 27d ago), licensed Apache-2.0. It adds 86 tokens to every session and 1,375 once invoked, about $0.0004 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…