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 Lab94/frenchie-skill --skill frenchie-methodgit 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/skills/lab94/frenchie-skill/frenchie-method)<a href="https://agentmods.dev/skills/lab94/frenchie-skill/frenchie-method"><img src="https://agentmods.dev/badge/skills/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/skills/lab94/frenchie-skill/frenchie-method"><img src="https://agentmods.dev/badge/skills/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.00036 | $0.01574 |
| Opus 5.5 | $0.00014 | $0.00630 |
| Sonnet 5.5 | $0.00007 | $0.00315 |
| Haiku 4.5 | $0.00004 | $0.00157 |
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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frenchie Method
Frenchie Method is the workflow/process layer. Frenchie Kit is the file and multimodal capability layer.
/frenchie-methodstarts Method orchestration./frenchieremains Frenchie Kit and must not be treated as a Method alias.- Text-only Method usage does not require a Frenchie API key.
- Install skills alongside MCP tools with
npx @lab94/frenchie install. - Codex Desktop exposes slash entrypoints by skill name, not by reading
.claude/commands/*.md. The Codex installer creates wrapper skills such asrequirement,qa-analysis, andimplementso/requirementcan work after restart. If a host does not expose those wrappers, treat no-slash requests such asFrenchie Method requirement ...as the corresponding Method command.
Runtime Defaults
Use .frenchie/method.config.json when present. If it is missing, continue with production-safe defaults:
- artifacts:
.frenchie/docs/feature - knowledge:
.frenchie/docs/knowledge - worktrees enabled by default
- orchestrator recommends the full sequence; direct commands warn-and-continue
- artifact language:
auto - cross-model review:
off - skill triggers: command-key skeleton is present; defaults are empty because installed skill sets vary by agent
Command Routing
The slash form below is the canonical Method command name. Claude Code reads command files directly. Codex uses wrapper skills with the same names. If the host agent does not support either path, recognize the same names without the leading slash when the user clearly asks to use Frenchie Method.
Tier 1 commands:
/frenchie-method
/method-check
/prepare-feature
/documenting-code
/requirement
/qa-analysis alias /test-case
/design conditional
/security-review
/sa-analysis alias /implementation-plan
/task-plan
/implement
/run-test
/walkthrough
/create-pr
/pr-review alias /review-pr
/quality-score
/fix-review
/systematic-debug alias /debug /fix-bug
/release-check
/release
/job-done
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 · 151 lines · 36 tokens per session scan A 042c48267acd
frenchie-method is a skill published in the GitHub repository Lab94/frenchie-skill (0 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 1,574 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…