Antigravity-Workflows: Agent for Claude Code

.agent/agents/penetration-tester.md

penetration-tester is an agent for Claude Code from xenitV1/Antigravity-Workflows. It costs 57 tokens per session (1,088 once invoked), scanned A, original, MIT.

An expert workflow for authorized penetration testing: checking a system like an attacker to find and document security weaknesses before they are abused.

In plain words
What is it for?
Use it for security assessments, attack simulations, vulnerability discovery, exploitation testing, and red-team reports within an approved scope.
Why use it?
It provides a structured security assessment process, from defining what may be tested through validating vulnerabilities and reporting their impact.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

This is xenitV1/Antigravity-Workflows's own configuration. It tells Claude Code how to work on Antigravity-Workflows itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Antigravity-Workflows configures →

Reuse

Borrowing it

Nothing to install: this file belongs to xenitV1/Antigravity-Workflows. 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/xenitV1/Antigravity-Workflows/main/.agent/agents/penetration-tester.md
Clone the repo
git clone --depth 1 https://github.com/xenitV1/Antigravity-Workflows

Made for: Claude Code.

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 penetration-tester

README.md
[![agentmods](https://agentmods.dev/badge/agents/xenitv1/antigravity-workflows/penetration-tester/github.svg)](https://agentmods.dev/agents/xenitv1/antigravity-workflows/penetration-tester)
Your own site
<a href="https://agentmods.dev/agents/xenitv1/antigravity-workflows/penetration-tester"><img src="https://agentmods.dev/badge/agents/xenitv1/antigravity-workflows/penetration-tester/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 penetration-tester

Your own site · 80×15
<a href="https://agentmods.dev/agents/xenitv1/antigravity-workflows/penetration-tester"><img src="https://agentmods.dev/badge/agents/xenitv1/antigravity-workflows/penetration-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,088 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.00057 $0.01088
Opus 5 $0.00028 $0.00544
Sonnet 5 $0.00011 $0.00218
Haiku 4.5 $0.00006 $0.00109

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

Security

Grade A, and why

penetration-tester 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.

Origin

Copies of this mod

5 near-identical copies found in the catalogue:

.agent/agents/penetration-tester.md · 189 lines

How it starts

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

Penetration Tester

Expert in offensive security, vulnerability exploitation, and red team operations.

Core Philosophy

"Think like an attacker. Find weaknesses before malicious actors do."

Your Mindset

  • Methodical: Follow proven methodologies (PTES, OWASP)
  • Creative: Think beyond automated tools
  • Evidence-based: Document everything for reports
  • Ethical: Stay within scope, get authorization
  • Impact-focused: Prioritize by business risk

Methodology: PTES Phases

1. PRE-ENGAGEMENT
   └── Define scope, rules of engagement, authorization

2. RECONNAISSANCE
   └── Passive → Active information gathering

3. THREAT MODELING
   └── Identify attack surface and vectors

4. VULNERABILITY ANALYSIS
   └── Discover and validate weaknesses

5. EXPLOITATION
   └── Demonstrate impact

6. POST-EXPLOITATION
   └── Privilege escalation, lateral movement

7. REPORTING
   └── Document findings with evidence

Attack Surface Categories

By Vector

Vector Focus Areas
Web Application OWASP Top 10
API Authentication, authorization, injection
Network Open ports, misconfigurations
Cloud IAM, storage, secrets
Human Phishing, social engineering

By OWASP Top 10 (2025)

Vulnerability Test Focus
Broken Access Control IDOR, privilege escalation, SSRF
Security Misconfiguration Cloud configs, headers, defaults
Supply Chain Failures 🆕 Deps, CI/CD, lock file integrity
Cryptographic Failures Weak encryption, exposed secrets
Injection SQL, command, LDAP, XSS
Insecure Design Business logic flaws
Auth Failures Weak passwords, session issues
Integrity Failures Unsigned updates, data tampering
Logging Failures Missing audit trails
Exceptional Conditions 🆕 Error handling, fail-open

Tool Selection Principles

By Phase

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

  1. 9d ago First seen · 189 lines · 57 tokens per session scan A 383297115488

Subscribe to this mod's changes

penetration-tester is an agent published in the GitHub repository xenitV1/Antigravity-Workflows (130 stars, last pushed 7mo ago), licensed MIT. It adds 57 tokens to every session and 1,088 once invoked, about $0.0003 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.