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.
git 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-functional)<a href="https://agentmods.dev/commands/jonase47/ccpr/p6-functional"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-functional/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.
<a href="https://agentmods.dev/commands/jonase47/ccpr/p6-functional"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-functional.svg" alt="Reviewed on agentmods" width="80" 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.00784 |
| Opus 5.5 | $0.00000 | $0.00314 |
| Sonnet 5.5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
p6-functional 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p6-functional – Integration, E2E & Regression Tests
Runs systematic functional tests at the system level. Each test level is a separate sub-command.
Argument: $ARGUMENTS = [test area/feature]
If provided: Test the specified area. If not provided: Read TEST_STRATEGY.md and ask about the test scope.
Flow
0. Ensure Sub-Index Exists
Make sure docs/quality/FUNCTIONAL.md exists as a sub-index with the standard header (Status / Last Updated / Key Decisions / Open Risks / Detail Files / Gate Notes — see ~/.claude/docs/PROJECT_PHASES.md). If missing, create it with empty placeholders. The three p6-func-* sub-commands below each refresh their own row in this sub-index's Detail Files table.
1. Integration Tests
/p6-func-integration $ARGUMENTS – Tests the interaction between system components.
2. E2E Tests
/p6-func-e2e $ARGUMENTS – Tests critical user journeys end-to-end.
3. Regression Tests
/p6-func-regression $ARGUMENTS – Ensures that existing functionality has not been broken.
4. Roll Up Sub-Index to Phase Index
After all p6-func-* sub-commands have run, summarise the FUNCTIONAL sub-index into the phase index docs/quality/QA.md:
- Add an entry in the phase-index Detail Files table for
[FUNCTIONAL.md](FUNCTIONAL.md)(the sub-index itself), statuscompleteonce all three sub-skill rows arecomplete(orneeds-rework). - Lift any blocking functional failure into the phase-index Open Risks.
Notes
- Maintain order: Integration → E2E → Regression
- On integration failures: Fix first before starting E2E
- Detail files:
func_integration.md,func_e2e.md,func_regression.mdunder theFUNCTIONAL.mdsub-index
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
/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.
- 1mo ago Changed · +1 lines 6a083b02ddad
- 1mo ago Changed 160328849638
- 1mo ago First seen · 56 lines · 0 tokens per session scan A a129a3f7a162
p6-functional is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 784 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
playwright-setup
Verify Playwright CLI installation and create a .playwright/cli.config.json configuration file. Use when setting up browser automation, configuring Playwright, or user mentions "setup playwright", "configure browser testing", "install playwright".
test-browser
Run browser tests on pages affected by current PR or branch.
test-suite
Run comprehensive test suite with coverage analysis.
health-check
Perform a comprehensive, read-only end-to-end review of any portfolio app across three layers — Frontend (E2E), Database integrity, and Audit Log & User Activity — and produce a structured, observations-only report. Optionally, on explicit opt-in, generate (never apply) the infrastructure provisions needed so future…
gba-test
$ARGUMENTS: test mode — game profile defines available modes (e.g., smoke, gameplay, save, stress, full, ai, battle, nav, custom ).
web-checklist
A checklist command for testing a website after a Git merge. It records checklist items in a file so progress can be viewed and individual checks can be marked complete.