pt-gaining-access

pt-gaining-access is a skill for Claude Code, Codex from santosomar/ethical-hacking-agent-skills. It costs 42 tokens per session (387 once invoked), scanned A, original, Apache-2.0.

A controlled security-testing procedure for proving whether a previously identified vulnerability can actually be exploited.

In plain words
What is it for?
Use it to validate proof-of-concept attacks, test privilege boundaries and network separation, measure reachable systems or data, and document remediation steps.
Why use it?
It replaces assumptions about risk with reproducible evidence while limiting disruption, data access, and lasting changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to validate proof-of-concept attacks, test privilege boundaries and network separation, measure reachable systems or data, and document remediation steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/santosomar/ethical-hacking-agent-skills/pt-gaining-access
Install

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.

Any agent
npx skills add santosomar/ethical-hacking-agent-skills --skill pt-gaining-access
Clone the repo
git clone --depth 1 https://github.com/santosomar/ethical-hacking-agent-skills

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.

agentmods badge for pt-gaining-access

README.md
[![agentmods](https://agentmods.dev/badge/skills/santosomar/ethical-hacking-agent-skills/pt-gaining-access/github.svg)](https://agentmods.dev/skills/santosomar/ethical-hacking-agent-skills/pt-gaining-access)
Your own site
<a href="https://agentmods.dev/skills/santosomar/ethical-hacking-agent-skills/pt-gaining-access"><img src="https://agentmods.dev/badge/skills/santosomar/ethical-hacking-agent-skills/pt-gaining-access/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.

agentmods 80×15 button for pt-gaining-access

Your own site · 80×15
<a href="https://agentmods.dev/skills/santosomar/ethical-hacking-agent-skills/pt-gaining-access"><img src="https://agentmods.dev/badge/skills/santosomar/ethical-hacking-agent-skills/pt-gaining-access.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 387 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.00387
Opus 5 $0.00021 $0.00193
Sonnet 5 $0.00008 $0.00077
Haiku 4.5 $0.00004 $0.00039

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

Security

Grade A, and why

pt-gaining-access 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 11d 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.

skills/pt-gaining-access/SKILL.md · 71 lines

What it actually says

Pen Test Gaining Access

Authorized Use Only

Only perform controlled exploitation on explicitly approved targets. Avoid destructive actions, production instability, and unnecessary data access. Stop immediately if impact exceeds rules of engagement.

Objectives

  1. Validate whether identified weaknesses are exploitable.
  2. Demonstrate business-relevant impact with minimum disruption.
  3. Capture reproducible evidence for remediation.

Workflow

  1. Select candidates:
    • Use only prioritized, in-scope findings from scanning
    • Confirm preconditions and rollback/safety plan
  2. Define proof-of-concept boundaries:
    • Minimal payloads to prove exploitability
    • No persistence unless separately authorized
  3. Execute controlled validation:
    • Record each step, command, and response
    • Confirm exploit chain and resulting access level
  4. Assess blast radius:
    • Determine reachable systems/data from obtained access
    • Validate privilege boundaries and segmentation controls
  5. Package evidence:
    • Reproduction steps
    • Impact statement in business terms
    • Immediate containment recommendations

Output Template

# Gaining Access Output

## Tested Vulnerability
- Identifier:
- Target:
- Preconditions:

## Validation Result
- Exploitable: Yes/No/Partial
- Access achieved:
- Impact observed:

## Evidence
- Reproduction steps:
- Logs/screenshots/artifacts:

## Risk Statement
- Technical impact:
- Business impact:
- Likelihood:

## Handoff
- Needed remediation owners:
- Retest criteria:

Quality Checks

  • PoCs are non-destructive and scoped.
  • Evidence is enough for independent reproduction.
  • Impact is clearly tied to business risk.
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.

  1. 11d ago First seen · 71 lines · 42 tokens per session scan A d5357890e76b

Subscribe to this mod's changes

pt-gaining-access is a skill published in the GitHub repository santosomar/ethical-hacking-agent-skills (24 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 387 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

skill-benchmark

Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.

HoangNguyen0403/agent-skills-standard · 16 tokens