gate-p0

A discovery-phase quality checkpoint that checks whether a project has enough problem, audience, competitor, and feasibility information to move into conception.

In plain words
What is it for?
Checking discovery documents, confirming required sections and decisions, identifying open risks, and deciding whether the project is ready for the next phase.
Why use it?
It creates a Go/No-Go decision from the project's discovery documents instead of relying on an informal judgment.

Command

Install

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.

agentmods
npx agentmods add commands/jonase47/ccpr/gate-p0
Clone the repo
git clone --depth 1 https://github.com/jonase47/ccpr
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,932 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01932
Opus 5 $0.00000 $0.00966
Sonnet 5 $0.00000 $0.00386
Haiku 4.5 $0.00000 $0.00193

Measured 2d ago against content hash 85084ee0e4cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gate-p0 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 2d 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.

commands/gate-p0.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/gate-p0 – Quality Gate 0: Discovery → Conception

Checks whether all criteria of the Discovery phase have been met and prepares the Go/No-Go Decision. No argument – this gate always checks the complete checklist.

No Argument ($ARGUMENTS not applicable)

Gate commands do not accept arguments. They always check the complete current project status.

Execution

1. Read Preflight Report

Read docs/.gate-preflight-p0.md as the primary source of information. This report contains:

  • Artefact existence (phase index + detail files), mandatory sections, frontmatter status (mechanically checked)
  • Content check (regex-based: problem statement, Target Audience, competitors, Feasibility)
  • Document summaries (via Ollama, if available)

If the preflight report does not exist or is older than 10 minutes, read the Discovery documents directly instead — always start with the phase index:

  1. docs/discovery/DISCOVERY.md (phase index) — gives you the detail-file table, key decisions, open risks.
  2. From the index's detail-file table, load only the detail files you need to confirm content:
    • docs/discovery/PROBLEM.md (problem statement, target audience, non-target groups)
    • docs/discovery/MARKET.md (market size, demand, competition, economic assessment)
    • docs/discovery/REGULATORY.md (DSGVO, sector-specific regulation, knock-out, traffic-light verdict)

1a. Constitution Inviolables (mandatory pre-gate)

If docs/CONSTITUTION.md exists, the preflight report (docs/.gate-preflight-p0.md) includes a section "Constitution Inviolables (Required Read)" with the project's non-negotiable rules.

These Inviolables are mandatory input for the gate:

  • Include the Inviolable bullets verbatim in the agent prompt (Step 2 below).
  • The agent must check each evaluated phase-decision against the Inviolables.
  • Any violation is an "Inviolable breach" — surface it explicitly in the verdict and treat it as a No-Go signal (Conditional Go only if the user explicitly waives; document the waiver).

Read the full file on GitHub · 137 lines

Changes

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.

  1. 2d ago First seen · 137 lines · 0 tokens per session scan A 85084ee0e4cf

Subscribe to this mod's changes

gate-p0 is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,932 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.