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 CocoRoF/Geny --skill draft_prgit clone --depth 1 https://github.com/CocoRoF/GenyWrote 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/cocorof/geny/draft_pr)<a href="https://agentmods.dev/skills/cocorof/geny/draft_pr"><img src="https://agentmods.dev/badge/skills/cocorof/geny/draft_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/skills/cocorof/geny/draft_pr"><img src="https://agentmods.dev/badge/skills/cocorof/geny/draft_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.00022 | $0.00453 |
| Opus 5.5 | $0.00009 | $0.00181 |
| Sonnet 5.5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
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 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
Draft PR
You are writing a pull request description for the changes the operator has staged. Workflow:
-
Inspect. Run these via
Bash:git status -s— what's changed?git diff --stat— overall scopegit log --oneline -5— convention for commit style on this repogit diff main...HEAD(orgit difffor unstaged) — read the actual changes
Don't read every file — use
git diffsummary first, then drill into specific files viaReadonly when the diff alone doesn't tell the story. -
Classify. What kind of change is this?
feat/fix/refactor/docs/test/chore. The repo's recent history (step 1) is the source of truth on convention. -
Title. One imperative-mood sentence under 70 characters, prefixed by the type. E.g.
feat(canvas): widen pipeline visualization to 21 stages. NO emoji, NO "feat!:" syntax unless the repo already uses it. -
Body. Three sections:
- Summary — 2–4 sentence prose describing what + why. Link to issue / cycle docs if the diff references one.
- Test plan — bullet list of test commands or manual steps.
- Risk — one sentence on rollback path or "additive — safe revert".
-
Output. Print the title on the first line, then a blank line, then the body. The operator will copy-paste into
gh pr create.
Don't invent context that isn't in the diff. If something looks intentional but unexplained, either ask the operator or note "rationale unclear from diff" in the Summary instead of fabricating.
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 · 22 tokens per session scan A e65032dfcd23
draft-pr is a skill published in the GitHub repository CocoRoF/Geny (11 stars, last pushed 16d ago), licensed Apache-2.0. It adds 22 tokens to every session and 453 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-31.
Other skills, from other repositories
git-workflow
Git branching, commits, and PR workflow following GitFlow conventions.
pr-creator
Create well-structured pull requests with proper descriptions and labels.
working-in-worktrees
Decides when agent work needs an isolated git worktree and how to create, enter, and clean one up safely. Use when starting code changes in a checkout that may be shared with another agent, dispatching a Linear task, executing a spec, or running any parallel work that mutates tracked files.
writing-changelogs
Writes human-friendly changelog entries and release notes. Use when populating changelog, preparing releases, or reviewing release notes quality.
ci-local-export
Daily CI Steward job: export this clone's git hook timings (how long git commit and git push took, and which pushes were killed at the tool ceiling) to the ci-steward-data branch, then trim the local timings file. A DorkOS scheduled skill that runs pnpm ci:local-export.
besimple-tiny-broccoli
Small-change wrapper: implement → run repo checks → atomic commit → run dedup (BASESHA..HEAD).