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.
npx agentmods add commands/jonase47/ccpr/p6-pentest-authgit clone --depth 1 https://github.com/jonase47/ccprWrote 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/commands/jonase47/ccpr/p6-pentest-auth)<a href="https://agentmods.dev/commands/jonase47/ccpr/p6-pentest-auth"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-pentest-auth.svg" alt="Measured on agentmods" 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.00000 | $0.00819 |
| Opus 5 | $0.00000 | $0.00409 |
| Sonnet 5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
p6-pentest-auth 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 2d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p6-pentest-auth – Auth & Session Attacks
Actively tests authentication: brute-force protection, token predictability, session invalidation, JWT confusion.
Argument: $ARGUMENTS = [auth endpoint/area]
If provided: Focus on the specified auth area. If not provided: Test the entire authentication.
Prerequisites
/p6-pentest-reconcompleted- Auth system implemented
Agent
- Type: pentester
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads in advance and delivers inline:
- From src/: Auth code (login, token generation, session handling)
- Recon results from previous step
- From SECURITY.md: Auth specification
Prompt Template
Goal: Actively test auth mechanisms for vulnerabilities in: [area]
Auth Code: [inline from src/]
Output Format: Table with max. 10 attack attempts:
# Attack Method Result Severity PoC Result: Successful / Not exploitable / Mitigated
Constraints:
- Auth attacks ONLY – no injection, no authz
- For each attempt: document approach, procedure, result
- PoC minimal and non-destructive
- For missing auth system: "N/A" is sufficient
Orchestrator Checkpoint
- Brute-force, tokens, sessions, JWT confusion tested?
- PoCs are reproducible?
Write Detail File
Write the result to docs/quality/pentest_auth.md (overwrite). Frontmatter:
---
phase: P6
subskill: pentest-auth
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Scope, ## Findings (auth attack 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_auth.md](pentest_auth.md)with statuscomplete. - Lift any successful auth bypass into Open Risks as Critical.
- Do not edit
QA.mddirectly.
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 skill 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
/cleanupinstead of growing the file further.
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.
- 2d ago First seen · 90 lines · 0 tokens per session scan A 4e09d8a667ae
p6-pentest-auth is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 819 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.
Other commands, from other repositories
auth-flow
Design authentication and authorization flow. Usage: /mindforge:auth-flow [--type oauth2|session|jwt] [--mfa] [--authz rbac|abac].
mindforge:cdn
Optimize CDN caching and invalidation strategy. Usage: /mindforge:cdn [service] [--target-hit-ratio 95%] [--multi-cdn] [--shield].
degrade
Design graceful degradation strategy with availability tiers. Usage - /mindforge:degrade [service] [--tiers 3] [--shed-at 80%].
graphql
Design GraphQL schema and resolver architecture. Usage - /mindforge:graphql [domain] [--style code-first|schema-first] [--federation].
cache
Design caching strategy with invalidation patterns. Usage - /mindforge:cache [service] [--pattern aside|through|behind] [--layers N].
events
Design event-driven message flow with ordering and delivery guarantees. Usage - /mindforge:events [domain] [--broker kafka|rabbitmq|sqs] [--guarantee at-least-once].