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 skills/fallow-rs/fallow/open-draft-prnpx skills add fallow-rs/fallow --skill open-draft-prgit clone --depth 1 https://github.com/fallow-rs/fallowWrote 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/fallow-rs/fallow/open-draft-pr)<a href="https://agentmods.dev/skills/fallow-rs/fallow/open-draft-pr"><img src="https://agentmods.dev/badge/skills/fallow-rs/fallow/open-draft-pr.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.00268 |
| Opus 5 | $0.00023 | $0.00134 |
| Sonnet 5 | $0.00009 | $0.00054 |
| Haiku 4.5 | $0.00005 | $0.00027 |
Grade A, and why
open-draft-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 4d 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
Open Review PR
This skill keeps its historical file/name for compatibility, but fallow PRs are ready for review by default. Do not open draft PRs unless the user explicitly asks for a draft.
Workflow:
- Review the changed files and confirm the scope.
- Run the smallest relevant validation for the touched area.
- Prepare a concise conventional commit message.
- Commit with signing if committing is requested.
- Push the branch.
- Open a ready PR with a high-signal conventional title and body.
Requirements:
- Use conventional commits.
- Use signed commits.
- Use a descriptive non-
codex/branch name, for examplefeat/<slug>,fix/<slug>,refactor/<slug>,docs/<slug>, orchore/<slug>. - Do not pass
--drafttogh pr createunless the user explicitly asks for a draft. - Do not add AI attribution.
- Summarize validation honestly if some checks were not run.
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.
- 4d ago First seen · 28 lines · 47 tokens per session scan A 1714fe48e541
open-draft-pr is a skill published in the GitHub repository fallow-rs/fallow (4,438 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 268 once invoked, about $0.0002 per session on Opus 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 skills, from other repositories
truecourse-hooks
Install, configure, or remove the TrueCourse pre-commit hook.
Biome
Biome 2.x — fast all-in-one web toolchain in Rust. Formats, lints, assists. Replaces Prettier + ESLint.
eslint-docs
ESLint 10.x — flat config, rules, plugins, formatters, parsers, CLI, Node.js API, custom rules, migration.
git-github
Git workflow and GitHub collaboration patterns including conventional commits, branch naming, PR workflow, and gh CLI usage. Use when creating commits, branches, or pull requests. TRIGGER when: git commit, branch, PR, pull request, merge, gh cli. DO NOT TRIGGER when: code implementation, testing, documentation without…
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
submit-pr-from-current-changes
Create a branch, commit existing local changes, push them, and open a pull request. Use when submitting current work as a PR.