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-func-e2egit 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-func-e2e)<a href="https://agentmods.dev/commands/jonase47/ccpr/p6-func-e2e"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-func-e2e.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 | $0.00000 | $0.00852 |
| Opus 5 | $0.00000 | $0.00426 |
| Sonnet 5 | $0.00000 | $0.00170 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
p6-func-e2e 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 today.
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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p6-func-e2e – E2E Tests for Critical Paths
Tests critical user journeys end-to-end – from start to the expected final result.
Argument: $ARGUMENTS = [journey/feature]
If provided: Test the specified journey. If not provided: Ask about the paths to be tested.
Prerequisites
- Integration tests passed (
/p6-func-integration) - USER_JOURNEYS.md and TEST_STRATEGY.md present
Agent
- Type: qa-tester
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads in advance and delivers inline:
- From USER_JOURNEYS.md: The journey to be tested (exact steps)
- From TEST_STRATEGY.md: Defined critical E2E paths
Prompt Template
Goal: Run E2E tests for: [journey/feature]
User Journey: [inline from USER_JOURNEYS.md]
Output Format: A step-by-step table per journey:
Step Action Expected Actual Status Overall result: PASSED / FAILED
Constraints:
- E2E tests ONLY (no unit, no integration tests)
- Test from the user's perspective, not from the code perspective
- Max. 5 journeys per run
Orchestrator Checkpoint
- All critical paths from TEST_STRATEGY.md covered?
- Failed steps clearly documented?
Write Detail File
Write the result to docs/quality/func_e2e.md (overwrite). Frontmatter:
---
phase: P6
subskill: func-e2e
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Scope, ## Test Results (table per journey), ## Failures Summary.
Update Sub-Index
Update docs/quality/FUNCTIONAL.md (the functional-testing sub-index, created by /p6-functional if missing):
- Set
**Last Updated:** <DD.MM.YYYY>. - In its Detail Files table: ensure a row for
[func_e2e.md](func_e2e.md)with statuscomplete(orneeds-reworkif blocking failures exist). - Lift any blocking journey failure into Open Risks of the sub-index.
- 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.
- today First seen · 88 lines · 0 tokens per session scan A 4329a716914e
p6-func-e2e is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 852 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
wiki-tune
Tune wiki schema and conventions interactively.
listen
Show what a given agent should read before coding, plus briefs/approvals mentioning it.
pseo-init
Use when: kullanıcı "yeni proje", "init", "proje kur", "yeni domain ekle", "scaffold" gibi ifadeler kullanır ya da /pseo-init çağırırsa. Also use when: portföye yeni bir SEO projesi alındı, projects/{slug}/ klasörü ve project.config.json dosyasının schemaya uygun ilk hâli üretilecek; brief'te slug + domain + market…
forge-insights
Analyze past sessions for error patterns, file activity, and recommendations.
forge-context-status
Report on current context window usage, cache health, and compaction recommendation. Read-only — does not compact.
CLAUDE
Each subdirectory is one engine verb dispatched by ../cli/cli.ts: / .ts exports a pure handler that resolves the vault, does its work through ../core/ primitives, and returns its own typed report. Commands stay thin — they compose core checks and builders; they do not reimplement them. The canonical output schema is…