A command for closing a completed testing engagement by moving its records into a permanent archive.

Use it after delivering a final report to archive an engagement and mark it closed. A new follow-up test can be opened separately.

It prevents finished work from being changed accidentally and checks that a final report exists before closing it.

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

Your own site

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

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

When invoked 856 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.00071	$0.00856
Opus 5	$0.00036	$0.00428
Sonnet 5	$0.00014	$0.00171
Haiku 4.5	$0.00007	$0.00086

Measured 9d ago against content hash 11878e03508b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

pt-archive 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 9d 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-archive/SKILL.md · 76 lines

How it starts

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

/pt-archive — Seal a Completed Engagement (meta)

Move a finished engagement folder from context/engagements/ into context/archive/ (immutable) and stamp engagement.md status: closed. The archive is a historical record — nothing writes there after sealing. (Analog of 10x-archive.)

When to use, when to skip

Use once the report is delivered and the engagement is done.
Skip if the engagement is still active, or you plan more testing — archive is one-way. For a follow-up test, seal this one, then open a retest with /pt-new --from <id>.

Initial Response

With <engagement-id>: proceed to Step 0.
Without: print Usage: /pt-archive <engagement-id>. and STOP.

Inputs

context/engagements/<id>/ — [blocking] (the folder to seal).
report/final-report.md — [blocking] (a delivered report is the precondition).

Process

Step 0: Validate preconditions

Engagement folder exists at context/engagements/<id>/, else error: engagement "<id>" not found. and STOP.
report/final-report.md exists, else error: no final report — run /pt-report first. and STOP.
context/archive/<id>/ does NOT already exist, else error: "<id>" already archived. and STOP.

Step 1: Seal

Stamp engagement.md: status: closed, updated: <today>.
Move context/engagements/<id>/ → context/archive/<id>/ (create context/archive/ if absent).

Outputs

The engagement folder relocated to context/archive/<id>/ with engagement.md status: closed.

Handoff

No next stage — the engagement is sealed. Suggest the retest path (copied for convenience), then STOP:

echo -n "/pt-new <id>-retest --from <id>" | pbcopy 2>/dev/null || echo -n "/pt-new <id>-retest --from <id>" | clip.exe 2>/dev/null || echo -n "/pt-new <id>-retest --from <id>" | xclip -selection clipboard 2>/dev/null || true

✓ Sealed engagement <id> → context/archive/<id>/  (status: closed)

The archive is immutable. For a follow-up, open a retest:
  → /pt-new <id>-retest --from <id>   (✓ copied to clipboard)

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

9d ago First seen · 76 lines · 0 tokens per session scan A 11878e03508b

Subscribe to this mod's changes

pt-archive is a skill published in the GitHub repository brovar/10x-pentest (3 stars, last pushed 27d ago), licensed Apache-2.0. It adds 71 tokens to every session and 856 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.

Project management

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

10x-pentest: Skill for Claude Code