What is p6-pentest-authz?

An authorisation security test for checking whether users can access data or actions that belong to someone else or require higher permissions. It also checks whether protected endpoints can be used without permission.

Use it to test IDOR vulnerabilities, horizontal and vertical privilege escalation, and unprotected API endpoints.

It finds access-control mistakes that could expose private data or privileged actions, even when login itself works.

p6-pentest-authz — Command for Claude Code by jonase47/ccpr

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.

Clone the repo

git clone --depth 1 https://github.com/jonase47/ccpr

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/jonase47/ccpr/p6-pentest-authz/github.svg)](https://agentmods.dev/commands/jonase47/ccpr/p6-pentest-authz)

Your own site

<a href="https://agentmods.dev/commands/jonase47/ccpr/p6-pentest-authz"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-pentest-authz/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/commands/jonase47/ccpr/p6-pentest-authz"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-pentest-authz.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 840 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.00000	$0.00840
Opus 5.5	$0.00000	$0.00336
Sonnet 5.5	$0.00000	$0.00168
Haiku 4.5	$0.00000	$0.00084

Measured 1mo ago against content hash 50b28f725f78, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

p6-pentest-authz 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 1mo 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.

commands/p6-pentest-authz.md · 91 lines

How it starts

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

/p6-pentest-authz – Authorisation & Access Control

Tests IDOR, horizontal/vertical privilege escalation, and unprotected endpoints.

Argument: $ARGUMENTS = [API/area]

If provided: Focus on the specified area. If not provided: Test all protected resources.

Prerequisites

/p6-pentest-auth completed
RBAC/authorisation implemented

Agent

Type: pentester
Model: sonnet

Context (Orchestrator prepares)

Orchestrator reads in advance and delivers inline:

From src/: Authorisation code (middleware, guards, ownership checks)
From API_SPEC.md: Protected endpoints and permission matrix
From SECURITY.md: Authorisation requirements

Prompt Template

Goal: Actively test authorisation for vulnerabilities in: [area]

Authorisation Code: [inline from src/]

Permission Matrix: [inline from API_SPEC.md / SECURITY.md]

Output Format: Table with max. 10 attack attempts:

# Attack Method Result Severity PoC

Types: IDOR, Horizontal Escalation, Vertical Escalation, Unprotected Endpoints

Constraints:

Authorisation attacks ONLY – no auth, no injection

PoC minimal and non-destructive

For missing authorisation (e.g. single-user app): "N/A" is sufficient

Orchestrator Checkpoint

IDOR and privilege escalation tested?
All protected endpoints checked?

Write Detail File

Write the result to docs/quality/pentest_authz.md (overwrite). Frontmatter:

---
phase: P6
subskill: pentest-authz
status: active
last_updated: <DD.MM.YYYY>
---

Body sections: ## Scope, ## Findings (authz/IDOR/privilege-escalation table with PoCs), ## Severity Summary.

Update Sub-Index

Update docs/quality/PENTEST.md:

Set **Last Updated:** <DD.MM.YYYY>.
In its Detail Files table: ensure a row for [pentest_authz.md](pentest_authz.md) with status complete.
Lift any privilege-escalation finding into Open Risks as Critical.

Handover Epilogue

Before writing. docs/HANDOVER.md is capped — the file states its own limit in its header (default: ≤5 KB / ~150 lines). Two rules follow from that, and neither is optional:

Replace this command's previous epilogue block, do not append a second one. Stacking is what pushes the file over; one command run has been measured adding 1021 B, ~20 % of the cap.
If the file is already near its cap, shorten before you add. Reading the cap sentence is not the same as measuring: check the actual size, and when there is no room, condense existing content or hand the user /cleanup instead of growing the file further.

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

1mo ago Changed 50b28f725f78
1mo ago First seen · 91 lines · 0 tokens per session scan A 3961e3a03652

Subscribe to this mod's changes

p6-pentest-authz is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 840 tokens. 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-09-03.

Backend and APIs Claude Code Security agentic-workflows ai-agents anthropic claude claude-code-agents

p6-pentest-authz