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/method-check)<a href="https://agentmods.dev/commands/lab94/frenchie-skill/method-check"><img src="https://agentmods.dev/badge/commands/lab94/frenchie-skill/method-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/method-check"><img src="https://agentmods.dev/badge/commands/lab94/frenchie-skill/method-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.00589 |
| Opus 5.5 | $0.00000 | $0.00236 |
| Sonnet 5.5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
method-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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/method-check
Read-only Method health check for the user's project and current feature.
Validate config schema/defaults, artifact existence, required sections, state sanity, stale artifacts, worktree path existence, branch alignment, skillTriggers, cross-model review settings, template validity, and the recommended next command.
When the recommended next command is /implement, also run the pre-implement contract:
- no unresolved
state.json.openQuestions[] - no non-canonical numbered artifacts
- no standalone Method-owned companion artifact such as
security-review.mdinstate.json.artifacts - task-type-specific required artifacts exist and are not stale:
new-feature/bug-fix:01-requirement.md,02-acceptance-criteria.md,03-test-case.md,04-implementation-plan.mdhotfix:01-requirement.md,02-acceptance-criteria.md,03-test-case.md;04-implementation-plan.mdis optional for SEV4documentation,refactor,tech-debt,dep-bump,spike:01-requirement.md
- user-facing work has
05-design.md - behavior, billing, security, logging, storage, and async lifecycle decisions do not contradict across artifacts
If state.json is invalid, include a repair state.json note in ## Risks / Blockers: regenerate it from the canonical artifacts with schemaVersion, artifactRoot, and artifacts.{file}.status plus artifacts.{file}.dependencies.
Decision Reconciliation
When the recommended next command is /implement, run a semantic consistency pass before recommending implementation:
- Scan critical nouns and decision terms across the artifact set: auth scopes, billing units, job lifecycle, storage policy, logging/PII, external service clients, feature flags, and user-visible UX.
- Flag stale decisions left behind after a direction change, such as an old OAuth scope or old data lifecycle policy that contradicts the latest requirement.
- Confirm
04-implementation-plan.mdhas a singleChosen Implementation Boundariesanswer for each important technical boundary. - If a contradiction is found, recommend artifact repair or
/redoof the stale stage before/implement; still allow user override after explicit confirmation.
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 · 46 lines · 0 tokens per session scan A 2d0ed32aa903
method-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 589 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
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
react-native
Command "react-native" from getsentry/toolkit, covering xcode build step (react-native xcode) and important notes.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.