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 skills add cenconq25/claude-code-app-studio --skill gate-checkgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/skills/cenconq25/claude-code-app-studio/gate-check)<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.
<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>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 | $0.00028 | $0.00856 |
| Sonnet 5 | $0.00011 | $0.00342 |
| Haiku 4.5 | $0.00006 | $0.00171 |
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 5d 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.
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— readproduction/stage.txtand 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-*.mdproduction/qa/smoke-*.mdproduction/perf/perf-profile-*.mdproduction/security/security-audit-*.mdproduction/assets/asset-audit-*.mdproduction/balance/balance-check-*.mdproduction/localization/loc-report-*.mddocs/tech-debt.mdproduction/qa/soak/[date]/summary.mdproduction/releases/release-checklist-*.mdproduction/releases/launch-checklist-*.mddocs/architecture/for ADR statusesproduction/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-prdswith PASS verdict. - No
proposedADRs blocking.
preproduction -> production
Required:
/test-setupcomplete 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.
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.
- 5d ago First seen · 245 lines · 56 tokens per session scan A cc23c3c5af67
gate-check is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 1,711 once invoked, about $0.0003 per session on Opus 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.
Other skills, from other repositories
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"…
cy-execute-task
Implement and verify an existing CompozyOS spec task, then update its tracking. Excludes review remediation.
team-qa
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.
gh-issue
Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.