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.
git clone --depth 1 https://github.com/Lab94/frenchie-skillWrote 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/lab94/frenchie-skill/release-check)<a href="https://agentmods.dev/commands/lab94/frenchie-skill/release-check"><img src="https://agentmods.dev/badge/commands/lab94/frenchie-skill/release-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/commands/lab94/frenchie-skill/release-check"><img src="https://agentmods.dev/badge/commands/lab94/frenchie-skill/release-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.00000 | $0.00440 |
| Opus 5.5 | $0.00000 | $0.00176 |
| Sonnet 5.5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
release-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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release-check
Read-only release readiness gate.
Check artifact freshness, tests, review findings, security/privacy approvals, changelog/docs needs, rollback plan, branch state, and deployment prerequisites. Record stale artifacts, missing approvals, and unresolved risks as blockers or warnings in 09-release-checklist.md. Method is warning-only here: /release-check must not block by itself, and /release may proceed only after the user explicitly confirms or accepts the risk.
Alias: /frenchie-release-check.
Artifact Contract
/release-check must produce or update 09-release-checklist.md in the active feature folder. It is read-only with respect to deploy/merge/cleanup actions, but it writes the readiness artifact.
Required 09-release-checklist.md sections:
CI/CD Status
Current CI checks, deployment automation, merge queue/protected branch state, and whether merge may deploy.
Tests
Automated and manual verification summary, including links or command output summaries from 06-test-report.md.
Migrations
Database, storage, queue, backfill, or data migration status. Say "none" only after checking.
Environment Variables
New, changed, or removed env vars/secrets and rollout ordering.
Feature Flags
Flags, kill switches, staged rollout controls, and default states.
Rollback
Rollback command/plan, data rollback constraints, and owner.
Deploy Note
Human-readable deploy note with user impact, timing, and monitoring focus.
Changelog
User-facing or internal changelog entry, or explicit reason none is needed.
Monitoring / Logging
Metrics, logs, dashboards, alerts, smoke checks, and post-deploy observation window.
Risks
Open risks, accepted risks, and blockers.
Approval
Named human approval status. /release-check may recommend approval but cannot approve for the user.
Output Contract
The command response should include:
## Release Readiness
## Checklist Artifact
## Blocking Items
## Warnings
## Required Approval
## Recommended Next Command
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 · 73 lines · 0 tokens per session scan A 64d7cc870636
release-check is a command published in the GitHub repository Lab94/frenchie-skill (0 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 440 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
publish
Publish oh-my-opencode to npm via GitHub Actions workflow.
rollback
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
ship
Deploy feature through automated staging validation to production with rollback testing.
deploy
Run the complete ClawBridge release process. This is the ONLY way to deploy — follow every step.
ci
Run CI validation, create PRs, and merge on green.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.