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/create-pr)<a href="https://agentmods.dev/commands/lab94/frenchie-skill/create-pr"><img src="https://agentmods.dev/badge/commands/lab94/frenchie-skill/create-pr/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/create-pr"><img src="https://agentmods.dev/badge/commands/lab94/frenchie-skill/create-pr.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.00418 |
| Opus 5.5 | $0.00000 | $0.00167 |
| Sonnet 5.5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
create-pr 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.
What it actually says
/create-pr
Create a pull request only when the user explicitly wants one.
Summarize scope, tests, risks, and artifact links. Do not merge. Respect local repository tooling and branch policy.
Alias: /frenchie-create-pr.
PR Description Template
Use this exact section order. Each section is required even if the answer is "none" — make absence explicit.
## Problem
What user-visible problem this PR addresses. One paragraph; link the relevant requirement (AC-NNN IDs from `02-acceptance-criteria.md`) where applicable.
## Solution
What changed and why this approach. Link the design (`05-design.md`) and the implementation plan (`04-implementation-plan.md`). Note any deviation from the plan and why.
## Testing
- New / updated tests: list with file paths.
- Manual verification: what was clicked, in what environment, with what result.
- Coverage gaps: anything intentionally not tested in this PR and why.
## Rollback
How to revert if this PR breaks production. Include: revert command or migration-down step, feature flag toggle if any, communication needed (oncall, customers).
## Flags
List any feature flags introduced, default state, owner, and the flip plan. "None" is acceptable when the change is unflagged.
## Artifact Links
- `01-requirement.md`
- `02-acceptance-criteria.md` (cite AC IDs covered)
- `03-test-case.md`
- `04-implementation-plan.md`
- `05-design.md` (UI changes only)
- `06-test-report.md`
- `09-release-checklist.md`
Method-only PRs (changes inside .frenchie/docs/feature/ only) may collapse the template to Problem + Solution + Artifact Links — there is nothing to test or roll back.
If the PR also touches code outside .frenchie/docs/feature/, use the full template — artifact edits ride along, but Testing / Rollback / Flags still apply to the code change.
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 · 50 lines · 0 tokens per session scan A da0cf4567889
create-pr 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 418 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
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.