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 skills add ulises-jeremias/agent-toolkit --skill pr-fallbackgit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/skills/ulises-jeremias/agent-toolkit/pr-fallback)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/pr-fallback"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/pr-fallback/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/skills/ulises-jeremias/agent-toolkit/pr-fallback"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/pr-fallback.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.00055 | $0.00417 |
| Opus 5.5 | $0.00022 | $0.00167 |
| Sonnet 5.5 | $0.00011 | $0.00083 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
pr-fallback 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
PR body — default when no repo template (WHAT)
When to use
- Remote is GitHub and
assistant(or a file search) shows noPULL_REQUEST_TEMPLATE/pull_request_templateunder.github/. - You need a reasonable default for
gh pr create --body-fileuntil the repo adds its own template.
Instructions
- Run
output-handshake: user confirms where the final description will live (e.g.body.mdforgh, paste-only) and that a human will review. - If the repository adds a template later, prefer the repo over this file.
- Copy sections from
references/pr-body-default.md, fill placeholders (issue id, test notes), and pass the path togithub-cli-workflow.
GitLab
If there is no .gitlab/merge_request_templates/, you may use the same Markdown structure in the merge request description for consistency, subject to the user’s destination choice (MR description field, file, etc.) and output-handshake.
What not to do
- Do not assume a PR is always in a specific ticket system; the file the user points to is wherever they said in the handshake.
References
references/pr-body-default.md— local copy of the default bodydevelopment-workflow— default PR validation and DoD expectationsgithub-cli-workflow— draft PR creationgitlab-cli-workflow— GitLab MRs
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 36 lines · 55 tokens per session scan A 4a57cea05792
pr-fallback is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 417 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
git-commit-conventional
Create Conventional Commit messages and execute safe git commits from working tree changes. Use when users ask to create a commit, write a conventional commit message, split broad changes into multiple commits, stage only parts of files, run pre-commit before committing, or perform a quick commit-time quality review…
git-workflow
Guided Git workflow assistant. Helps with branching strategies, writing conventional commits, opening pull requests, resolving merge conflicts, and keeping history clean. TRIGGER when the user writes /git-workflow or asks for help with Git, branches, commits, PRs, or merge conflicts.
git-commit
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive…
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.