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-func-integration)<a href="https://agentmods.dev/commands/jonase47/ccpr/p6-func-integration"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-func-integration/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-func-integration"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-func-integration.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.01243 |
| Opus 5.5 | $0.00000 | $0.00497 |
| Sonnet 5.5 | $0.00000 | $0.00249 |
| Haiku 4.5 | $0.00000 | $0.00124 |
Grade A, and why
p6-func-integration 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p6-func-integration – Run Integration Tests
Tests the interaction between system components: API against DB, middleware chains, external services against mocks.
Argument: $ARGUMENTS = [test area/feature]
If provided: Focus on the specified area. If not provided: Ask about the test scope.
Prerequisites
- Implementation complete (P5 done)
- TEST_STRATEGY.md present
Agent
- Type: qa-tester
- Model: sonnet
Context (Orchestrator prepares)
The qa-tester agent has no Bash (agents/qa-tester.md) — it can design and write integration
test files (it has Write/Edit) but cannot execute them. That splits this command into two steps:
the agent designs the tests first, then the orchestrator runs them and hands the results back for
analysis. Prepared before step 1:
- From TEST_STRATEGY.md: Integration test level, tools, scope
- From ARCHITECTURE.md: Component diagram, interfaces (relevant section only)
- From API_SPEC.md: Endpoints to be tested
Prompt Template
Step 1: Design & write the tests (qa-tester)
Goal: Design and write integration tests for: [area]. Do not claim any test has passed or failed at this stage — results come from step 2 below, run by the orchestrator.
Components and Interfaces: [inline from ARCHITECTURE.md / API_SPEC.md]
Output Format: Table with max. 20 test cases:
# Test Case Components Expected Plus the path(s) of the test file(s) written. Constraints:
- Integration tests ONLY (no unit, no E2E)
- Focus on interfaces between components
- Test external services against mocks
Step 2: Execute (orchestrator, not the agent)
Run ~/.claude/scripts/run-tests.sh [new integration test path] [projectdir] against the file(s)
step 1 wrote and capture the JSON result.
Step 3: Report (qa-tester analyzes the results)
Goal: Fill in the Actual/Status columns for the table from step 1, using only the results below — transcribed, never estimated.
Results (from
scripts/run-tests.sh, already executed by the orchestrator): [inline JSON: framework, summary.total/passed/failed, failures[]]No-summary fallback: if the results carry no
summaryfield (run-tests.sh'snpm testpath returns{"framework":"npm-test","raw_output":…}, and an undetected framework returns{"framework":"unknown","error":…}) — do not produce any pass/fail count. Mark every row "Manually Verified" / "No parseable automated result" instead, and say so explicitly in the summary.Output Format: The step 1 table, extended:
# Test Case Components Expected Actual Status Summary (derived from the results'
summary): X passed, Y failed — or "Manually Verified" / "No parseable automated result" per the fallback above
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 · +31 lines 4e8d07bf00da
- 1mo ago Changed d01d7735f499
- 1mo ago First seen · 88 lines · 0 tokens per session scan A 3203580beb18
p6-func-integration 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 1,243 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.