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/cross-checkgit clone --depth 1 https://github.com/jonase47/ccprWhat 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.02268 |
| Opus 5 | $0.00000 | $0.01134 |
| Sonnet 5 | $0.00000 | $0.00454 |
| Haiku 4.5 | $0.00000 | $0.00227 |
Grade A, and why
cross-check 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 yesterday.
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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cross-check – Cross-Artifact Consistency Check Across Phases
Reads phase indexes and selected detail files, checks inconsistencies between phases (architecture ↔ implementation, features ↔ stories, threats ↔ mitigations, etc.).
Bridges the gap between intra-phase lints (phase-docs-lint.sh) and gate content evaluation —
finds contradictions no other skill surfaces.
Recommendation, not a mandatory step. Gates list /cross-check as an optional pre-flight check.
Argument: $ARGUMENTS = [optional: projectdir]
- Without argument: operates on
$(pwd).
Prerequisites
- Project has at least 2 completed phases (otherwise there is no "cross")
- Phase indexes exist:
docs/discovery/DISCOVERY.md,docs/concept/CONCEPT.md,docs/architecture/ARCHITECTURE.md,docs/planning/PROJECT_PLAN.md, optionallydocs/quality/QA.md - Optional:
docs/CONSTITUTION.md(for R6)
Lead Agent
code-reviewer with system-architekt as consultant for tech-specific findings.
Rule Catalogue v1 (7 Rules)
R1: FEATURES.md ↔ AUTH.md / User-Stories
Every user-facing feature (login, profile, permissions) must have a corresponding flow in AUTH.md.
Sources:
docs/concept/FEATURES.md(feature list, MoSCoW)docs/architecture/AUTH.md(auth flows)docs/planning/BACKLOG.md(user stories as cross-reference)
Check: For each feature tagged as user-facing (heuristic: mentions "login", "account", "profile", "sign-in") → is a matching flow described in AUTH.md?
R2: TECH_STACK.md ↔ DATA_MODEL.md (DB choice consistent)
If TECH_STACK.md names PostgreSQL, DATA_MODEL.md must not use MongoDB syntax (and vice versa).
Sources:
docs/architecture/TECH_STACK.md(DB choice, language, framework)docs/architecture/DATA_MODEL.md(schema, ERD)docs/architecture/API_SPEC.md(endpoints)
Check: Extract DB term from TECH_STACK (regex PostgreSQL|MongoDB|SQLite|SwiftData|MySQL); search DATA_MODEL for syntax markers (CREATE TABLE, NoSQL JSON schema, @Model SwiftData decorators). Report inconsistencies.
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.
- yesterday First seen · 199 lines · 0 tokens per session scan A fde93002221d
cross-check is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,268 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-08-31.
Other commands, from other repositories
drift
Post-implementation spec drift check — verify the implementation matches existing OpenSpec specifications.
feature
Orchestrate a complete feature through discovery, spec, implementation, and review.
research
Research a technical or product question.
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.
clean-check
Analyze code for cleanliness issues (unused code, comment quality, formatting, naming, complexity). Delegates to the code-cleanliness agent.
build
Mini spec-first development workflow for well-scoped implementation tasks with human in the loop.