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/prd-routergit 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.00311 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
prd-router 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 2d 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.
What it actually says
PRD Command Router
Routes to Frenchie Method. This file backs PRD command names that are recognized now but may initially be template-backed or wrappers around production-depth commands.
When invoked through any copied command filename, identify the requested command name, map it to the nearest production-depth command, and preserve the requested command in the artifact note.
Routing:
- Requirement family:
/refine-requirement,/user-story,/scope-check,/open-questions,/stakeholder-summary->/requirement - Analysis family:
/impact-analysis,/api-design,/db-design,/architecture-review->/sa-analysis - Risk family:
/risk-analysis->/security-review - QA family:
/regression-test,/e2e-scenario,/test-data,/write-unit-test->/qa-analysis - Debug family:
/bug-repro,/incident-report->/systematic-debug - Docs/release family:
/update-docs->/task-plan;/performance-review->/pr-review;/rollback-plan,/changelog->/release-check;/postmortem->/job-done
Every command also supports its prefixed alias, for example /frenchie-api-design and /frenchie-changelog.
Direct invocation behavior follows Method direct-skill mode: warn when required artifacts are missing, recommend the safer next Method command, ask whether to continue from chat/repo context, and record the caveat when feature state exists.
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.
- 2d ago First seen · 19 lines · 0 tokens per session scan A 315fe2261179
prd-router 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 311 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.
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.