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 agentmods add skills/lab94/frenchie-skill/frenchie-methodnpx skills add Lab94/frenchie-skill --skill frenchie-methodgit clone --depth 1 https://github.com/Lab94/frenchie-skillWhat 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 | $0.00036 | $0.01574 |
| Opus 5 | $0.00018 | $0.00787 |
| Sonnet 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 yesterday.
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.
- yesterday 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 3mo ago), licensed MIT. It adds 36 tokens to every session and 1,574 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.