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-integrationgit 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.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.00795 |
| Opus 5 | $0.00000 | $0.00398 |
| Sonnet 5 | $0.00000 | $0.00159 |
| Haiku 4.5 | $0.00000 | $0.00080 |
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 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-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)
Orchestrator reads in advance and delivers inline:
- 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
Goal: Write and run integration tests for: [area]
Components and Interfaces: [inline from ARCHITECTURE.md / API_SPEC.md]
Output Format: Table with max. 20 test cases:
# Test Case Components Expected Actual Status Summary: X passed, Y failed
Constraints:
- Integration tests ONLY (no unit, no E2E)
- Focus on interfaces between components
- Test external services against mocks
Orchestrator Checkpoint
- All critical interfaces tested?
- Failed tests are reproducible?
Write Detail File
Write the result to docs/quality/func_integration.md (overwrite). Frontmatter:
---
phase: P6
subskill: func-integration
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Scope, ## Test Results (table), ## Failures Summary.
Update Sub-Index
Update docs/quality/FUNCTIONAL.md:
- Set
**Last Updated:** <DD.MM.YYYY>. - In its Detail Files table: ensure a row for
[func_integration.md](func_integration.md)with statuscomplete. - Lift any blocking integration failure into Open Risks.
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 3203580beb18
p6-func-integration 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 795 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
tidy
Consistency check for non-code repos with INDEX.md hierarchy. Verifies INDEX.md accuracy, MEMORY.md references, orphaned files, stale dates, and WAITING markers.
wiki-tune
Tune wiki schema and conventions interactively.
listen
Show what a given agent should read before coding, plus briefs/approvals mentioning it.
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…