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/frenchie-method)<a href="https://agentmods.dev/commands/lab94/frenchie-skill/frenchie-method"><img src="https://agentmods.dev/badge/commands/lab94/frenchie-skill/frenchie-method/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/frenchie-method"><img src="https://agentmods.dev/badge/commands/lab94/frenchie-skill/frenchie-method.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.01285 |
| Opus 5.5 | $0.00000 | $0.00514 |
| Sonnet 5.5 | $0.00000 | $0.00257 |
| Haiku 4.5 | $0.00000 | $0.00128 |
Grade A, and why
frenchie-method 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/frenchie-method
Orchestrate Frenchie Method. Classify the task, resolve or create feature context, check config/state/artifact freshness, and recommend the next Method command. Stop for user approval at risk points. The orchestrator emits warnings but never blocks — direct command invocation always overrides its recommendations.
Do not treat /frenchie as an alias. /frenchie is Frenchie Kit.
Flow:
- Identify task type:
new-feature,bug-fix,hotfix,documentation,spike,refactor,tech-debt, ordep-bump. - Detect whether the user made a freeform implementation request: Method was invoked in any form while also asking to build, change, edit, code, or implement.
- Resolve
.frenchie/method.config.json; use defaults if missing. - Locate or propose the feature artifact folder.
- Check stale artifacts, branch/worktree alignment, and missing recommended artifacts.
- Consult the selected workflow as the source of truth, recommend exactly one next Method command, and execute it on user confirmation.
- Never execute
/releaseautomatically.
Freeform implementation request handling
When the user invokes /frenchie-method, a Method wrapper skill, or the phrase Frenchie Method and also asks for implementation in the same request, the orchestrator routes into the selected Method workflow before production edits. It does not become a generic coding agent just because the implementation intent is clear.
For these requests, do not edit production code, create a feature branch, or start ordinary implementation until one of these is true:
- Feature context exists and the minimum artifact set is present:
state.json,01-requirement.md,02-acceptance-criteria.md,03-test-case.md, and04-implementation-plan.md. - For user-facing marketing, frontend, content, UI, navigation, page, component, or flow work,
05-design.mdis also present. - The user explicitly approves a documented skip after the orchestrator names the missing artifacts and risk.
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 · 92 lines · 0 tokens per session scan A 05adb07a0b29
frenchie-method 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 1,285 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.