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/fusengine/agentsWrote 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/fusengine/agents/create-pull-request)<a href="https://agentmods.dev/commands/fusengine/agents/create-pull-request"><img src="https://agentmods.dev/badge/commands/fusengine/agents/create-pull-request/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/fusengine/agents/create-pull-request"><img src="https://agentmods.dev/badge/commands/fusengine/agents/create-pull-request.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.00022 | $0.00360 |
| Opus 5.5 | $0.00009 | $0.00144 |
| Sonnet 5.5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
create-pull-request 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 Pull Request
Generate and create a comprehensive Pull Request:
-
Analyze Branch Changes:
git log main..HEAD --oneline git diff main...HEAD --stat -
Extract Commit Information:
- Parse all commit messages since branch diverged from main
- Identify key features/fixes/changes
- Categorize changes (Features, Bug Fixes, Documentation, etc.)
-
Generate PR Description:
## Summary [Concise overview of changes] ## Changes - ✨ Feature: [Description] - 🐛 Fix: [Description] - 📚 Docs: [Description] ## Test Plan - [ ] Unit tests pass (`bun test`) - [ ] Linters pass (`bun run lint`) - [ ] Manual testing completed - [ ] [Specific test scenario] ## Breaking Changes [None / List any breaking changes] ## Screenshots [If applicable] -
Create PR:
gh pr create --title "[TITLE]" --body "$(cat <<'EOF' [GENERATED DESCRIPTION] EOF )" -
Output PR URL
Arguments:
- $ARGUMENTS will be used as PR title or additional context
Example Usage:
/create-pull-request Add authentication→ Creates PR with title/create-pull-request→ Auto-generates title from commits
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 · 61 lines · 22 tokens per session scan A 903c162c0e16
create-pull-request is a command published in the GitHub repository fusengine/agents (31 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 360 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-30.
Other commands, from other repositories
nyann:doctor
Run nyann's read-only hygiene + documentation audit on the current repo. Emits the same drift sections retrofit uses, but never offers remediation or writes to the filesystem. Use this on session start, in CI, or any time you want to sanity-check a repo without risking mutations.
nyann:retrofit
Audit an existing repo against a profile and fix what's drifted. Unlike doctor (read-only), retrofit detects missing hooks, misconfigured gitignore, documentation gaps, and non-compliant history, then offers to remediate via bootstrap. Idempotent — safe to re-run.
nyann:cleanup-branches
Prune local branches whose work is already merged into the base. Lists candidates first, then applies on --yes. Mirrors the safe-delete semantics of git branch -d (lowercase d): nothing unmerged is touched.
nyann:commit
Generate a Conventional Commits message from the staged diff and commit after confirmation. Same flow as the natural-language commit skill — dispatches here so users who prefer explicit slash commands can bypass intent detection.
nyann:pr
Open a GitHub pull request from the current branch. Pushes with -u tracking, then invokes gh pr create. Requires gh installed + authed.
init-ledger
(Ledger) Create the ledger repository — Registry + Config — the one-time setup.