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-regressiongit 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-regression)<a href="https://agentmods.dev/commands/jonase47/ccpr/p6-func-regression"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-func-regression.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-regression 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-regression – Run Regression Tests
Ensures that existing functionality has not been broken by new changes.
Argument: $ARGUMENTS = [area/sprint]
If provided: Focus regression on the specified area. If not provided: Test all areas affected by the latest changes.
Prerequisites
- Existing automated tests present
- SPRINT.md with latest changes
Agent
- Type: qa-tester
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads in advance and delivers inline:
- From SPRINT.md: Which features/modules were changed most recently
- From tests/: Existing test files (file names + test case overview only)
Prompt Template
Goal: Run regression tests – check whether recent changes have broken existing functionality
Recent Changes: [inline from SPRINT.md]
Output Format:
# Test Area Total Tests Passed Failed Regressions New regressions (if any):
# Regression Affected Feature Suspected Cause Constraints:
- Run existing tests ONLY, do not write new ones
- Focus on areas affected by recent changes
- Assign each regression clearly to a change
Orchestrator Checkpoint
- All existing tests executed?
- Regressions clearly documented and assigned?
Write Detail File
Write the result to docs/quality/func_regression.md (overwrite). Frontmatter:
---
phase: P6
subskill: func-regression
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Scope, ## Test Results (table), ## Regressions Detected.
Update Sub-Index
Update docs/quality/FUNCTIONAL.md:
- Set
**Last Updated:** <DD.MM.YYYY>. - In its Detail Files table: ensure a row for
[func_regression.md](func_regression.md)with statuscomplete. - Lift any newly detected regression into Open Risks with assignment.
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 373ca260dd23
p6-func-regression 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
research
Research a technical or product question.
status
Show Hydra framework status — installed agents, version, config, and update availability.
prd
Generate a Product Requirements Document for an team squad. Business-facing artifact. Sensors and evals gate.
pseo-cannibalization
Use when: kullanıcı "cannibalization", "kannibalizasyon", "keyword conflict", "URL çakışması", "aynı keyword'e iki sayfa", "anahtar kelime çakışması", "iki sayfam aynı sorguya çıkıyor", "intent split" der ya da /pseo-cannibalization çağırırsa. Also use when: aktif projenin GSC verisi mevcut (gsc-pull önce çalışmış)…
forge-insights
Analyze past sessions for error patterns, file activity, and recommendations.
pippen
Stability, Integration & Defense — ensures components work together and stay working in production.