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 commands/lab94/frenchie-skill/prepare-featuregit 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.00000 | $0.00525 |
| Opus 5 | $0.00000 | $0.00262 |
| Sonnet 5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
prepare-feature 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/prepare-feature
Create or resolve feature working context.
Responsibilities:
- Choose a stable feature slug.
- Create
.frenchie/docs/feature/<feature>/when the user confirms. - Initialize
state.jsonwith task type, current stage, branch/worktree metadata, and artifact map. - Recommend a git worktree when
worktree.enabledis true. - Ask before destructive cleanup or overwriting stale state.
Alias: /frenchie-prepare-feature.
Worktree Edge Behavior
Default policy:
new-feature: branch prefixfeature/bug-fix: branch prefixfix/hotfix: branch prefixhotfix/documentation: branch prefixdocs/spike: branch prefixspike/refactor: branch prefixrefactor/tech-debt: branch prefixchore/dep-bump: branch prefixdeps/
Branch defaults may be overridden by .frenchie/method.config.json, but the command must state the resolved branch before creating it.
Collision handling:
- Use the configured
pathPatternfirst. - If the target path already exists, choose a deterministic suffix collision strategy:
-2,-3, etc. Do not use timestamps or random suffixes unless the user explicitly asks. - If the existing path is the intended worktree, reuse it only after confirming branch and repository alignment.
Repository/worktree detection:
- Resolve the intended git repository root before generating artifact or worktree paths. In monorepos or nested repository setups, prefer the nearest git root that owns the files in scope and ask when ambiguous.
- Detect nested worktree paths and warn when the proposed worktree would sit inside another worktree or inside the active repository.
- If
git worktree listcontains stale entries whose paths no longer exist, warn and suggestgit worktree prune. Do not run prune without explicit user approval. - If a listed worktree path exists but points at a different repository, stop and ask for a path/branch decision.
Failure and cleanup policy:
- On filesystem failure, fall back to a no-worktree feature folder in the current checkout, record the caveat in
state.json, and ask before retrying with a different path. - Ask before deleting directories, removing worktrees, pruning stale git worktree metadata, deleting branches, or overwriting existing Method state.
- Worktree cleanup belongs near
/job-done, not/prepare-feature, unless the user explicitly asked to repair setup.
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 · 48 lines · 0 tokens per session scan A 8d348857be2e
prepare-feature is a command published in the GitHub repository Lab94/frenchie-skill (0 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 525 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.