Borrowing it
Nothing to install: this file belongs to TheAstrelo/Claude-Pipeline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TheAstrelo/Claude-Pipeline/main/.claude/commands/pmatch.mdgit clone --depth 1 https://github.com/TheAstrelo/Claude-PipelineWrote 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/theastrelo/claude-pipeline/pmatch)<a href="https://agentmods.dev/commands/theastrelo/claude-pipeline/pmatch"><img src="https://agentmods.dev/badge/commands/theastrelo/claude-pipeline/pmatch/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/theastrelo/claude-pipeline/pmatch"><img src="https://agentmods.dev/badge/commands/theastrelo/claude-pipeline/pmatch.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.00564 |
| Opus 5.5 | $0.00000 | $0.00226 |
| Sonnet 5.5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade B, and why
pmatch scanned grade B with 1 finding 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 2mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
SESSION_DIR=$(cat .claude/artifacts/current.txt 2>/dev/null) How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify plan-design alignment before build.
Prerequisites
Check that both design and plan exist:
SESSION_DIR=$(cat .claude/artifacts/current.txt 2>/dev/null)
if [ -z "$SESSION_DIR" ]; then
echo "ERROR: No active session. Run /arm first."
exit 1
fi
if [ ! -f "$SESSION_DIR/design.md" ]; then
echo "ERROR: No design.md found. Run /design first."
exit 1
fi
if [ ! -f "$SESSION_DIR/plan.md" ]; then
echo "ERROR: No plan.md found. Run /plan first."
exit 1
fi
Drift Detection
Use the drift-detector agent.
Input:
- Read
design.mdfrom the current session directory - Read
plan.mdfrom the current session directory
Process:
-
Extract all design requirements:
- Components to create
- APIs to implement
- Database changes
- Behavior specifications
- Error handling requirements
-
Map each requirement to plan step(s)
-
Check for drift types:
- Missing Coverage: Design requirement not in plan
- Scope Creep: Plan step not justified by design
- Contradictions: Plan conflicts with design
- Incomplete Steps: Plan step missing required detail
-
Output
drift-report.md
Verdict Rules
ALIGNED if:
- All design requirements covered
- No unjustified scope creep
- No contradictions
- All steps complete
DRIFT_DETECTED if:
- Any requirement uncovered
- Unjustified scope creep
- Any contradiction
- Critical incomplete step
Output
After detection, report:
## Drift Detection Complete
**Session:** {session-directory}
**Verdict:** [ALIGNED | DRIFT_DETECTED]
### Coverage
- Design requirements: [N]
- Covered by plan: [N]
- Missing: [N]
### Issues Found
[List any drift issues]
### Next Step
[If ALIGNED] Run `/build` to implement the plan.
[If DRIFT_DETECTED] Fix the drift issues:
- Missing coverage: Update /plan
- Scope creep: Justify or remove
- Contradictions: Resolve which is correct
User Override
If drift is detected but the user wants to proceed anyway:
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.
- 2mo ago First seen · 115 lines · 0 tokens per session scan B 01bde36ef964
pmatch is a command published in the GitHub repository TheAstrelo/Claude-Pipeline (47 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 564 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
scout-work
Interactive work session — walks through today's actionable items one at a time, presents a recommended action with draft content, and executes each one only with explicit approval. Runs in the current conversation (not as a background session).
pause
Checkpoint the ticket in play so it can be resumed later.
audit
Audit closed tickets for regressions against today's code (unchanged, evolved, implemented wrong, not implemented), plus duplicate and groupable open ones.
dashboard
Show the repo dashboard: the pinned index of every open map, the whiteboard, and live counts.
split
Split an oversized ticket into children and supersede it.