A phase-readiness check that combines recent quality, performance, security, asset, balance, localization, and release findings into one decision.

It checks the relevant project records and reports PASS, CONCERNS, or FAIL with specific blockers and required artifacts.

It shows whether a project can move to its next development phase and identifies missing or outdated evidence.

gate-check — Skill for Claude Code by cenconq25/claude-code-app-studio

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.

Any agent

npx skills add cenconq25/claude-code-app-studio --skill gate-check

Clone the repo

git clone --depth 1 https://github.com/cenconq25/claude-code-app-studio

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/gate-check/github.svg)](https://agentmods.dev/skills/cenconq25/claude-code-app-studio/gate-check)

Your own site

<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/gate-check"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/gate-check/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/gate-check"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/gate-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,711 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00056	$0.01711
Opus 5.5	$0.00022	$0.00684
Sonnet 5.5	$0.00011	$0.00342
Haiku 4.5	$0.00006	$0.00171

Measured 1mo ago against content hash cc23c3c5af67, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gate-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 1mo 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.

.claude/skills/gate-check/SKILL.md · 245 lines

How it starts

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

Gate Check

Phase advancement requires more than vibes. This skill collects every recent verdict artifact, cross-checks them for staleness and consistency, and emits a single PASS / CONCERNS / FAIL ruling. It is intentionally cross-system synthesis — therefore Opus tier.

Phase 1: Determine Source and Target Phase

Parse the argument:

Explicit form: prototype->preproduction, preproduction->production, production->polish, polish->release, release->live-ops.
--auto — read production/stage.txt and use the next standard transition.
No argument — ask the user.

Each gate has a different artifact bar (see Phase 3).

Phase 2: Inventory Recent Artifacts

Glob the latest of each artifact type:

production/qa/qa-signoff-*.md
production/qa/smoke-*.md
production/perf/perf-profile-*.md
production/security/security-audit-*.md
production/assets/asset-audit-*.md
production/balance/balance-check-*.md
production/localization/loc-report-*.md
docs/tech-debt.md
production/qa/soak/[date]/summary.md
production/releases/release-checklist-*.md
production/releases/launch-checklist-*.md
docs/architecture/ for ADR statuses
production/qa/bugs/ for open S1/S2 counts

For each, capture: path, last modified date, verdict.

Apply staleness rule: any artifact older than 14 days is suspect for a release-tier gate. Flag and surface.

Phase 3: Apply the Gate-Specific Bar

prototype -> preproduction

Required:

Architecture artifacts present (docs/architecture/master-architecture.md, ADRs, control manifest).
All MVP PRDs reviewed via /review-all-prds with PASS verdict.
No proposed ADRs blocking.

preproduction -> production

Required:

/test-setup complete and CI runs green.
Foundation epics done.
First sprint plan approved.

production -> polish

Required:

All Critical / Must-Have features implemented per PRD.
Latest QA sign-off APPROVED on the most recent sprint.
Open S1/S2 bugs == 0.
Tech debt register reviewed in last 30 days.

Read the full file on GitHub · 245 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.

1mo ago First seen · 245 lines · 56 tokens per session scan A cc23c3c5af67

Subscribe to this mod's changes

gate-check is a skill published in the GitHub repository cenconq25/claude-code-app-studio (42 stars, last pushed 5mo ago), licensed MIT. It adds 56 tokens to every session and 1,711 once invoked, about $0.0002 per session on Opus 5.5. 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.

Project management Testing

team-qa

Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.

Donchitos/Claude-Code-Game-Studios · 35 tokens

scaffold-dotnet-test-project

MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero"…

dotnet/skills · 138 tokens

test-result-feedback

Close the acceptance loop for a tested change — consume the apc test TierResult, map EACH acceptance criterion to a pass/fail outcome from structured fields (never chat text), attach an evidence ref, and write it back to the task. A SUT red is a finding, never softened to green.

Prismer-AI/PrismerCloud · 65 tokens

gate-check

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Gate Check

Phase 1: Determine Source and Target Phase

Phase 2: Inventory Recent Artifacts

Phase 3: Apply the Gate-Specific Bar

prototype -> preproduction

preproduction -> production

production -> polish

What this file has done since we first saw it

Other skills, from other repositories

team-qa

scaffold-dotnet-test-project

test-result-feedback

conductor-implement

cy-execute-task

implement-feature