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/cocorof/geny/draft_prnpx skills add CocoRoF/Geny --skill draft_prgit clone --depth 1 https://github.com/CocoRoF/GenyWhat 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.00022 | $0.00453 |
| Opus 5 | $0.00011 | $0.00227 |
| Sonnet 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 2d 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.
- 2d ago First seen · 36 lines · 22 tokens per session scan A e65032dfcd23
draft-pr is a skill published in the GitHub repository CocoRoF/Geny (10 stars, last pushed 4d ago), licensed Apache-2.0. It adds 22 tokens to every session and 453 once invoked, about $0.0001 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-31.
Other skills, from other repositories
agent_management
This Skill provides a complete management guide for OpenSquad Agents, covering the full workflow of creation, configuration, deployment, and troubleshooting.
Collaboration Management
Complete guide to multi-agent collaboration card management, including starting collaborations, joining teams, and creating custom collaboration cards.
collaboration-workflow
Complete guide to the OpenSquad multi-agent collaboration system with user authorization gates. Use this skill when starting a collaboration session, coordinating multiple agents, managing the collaboration board, or when you need to understand how to use boardupdate, boardlist, and other collaboration tools. Triggers…
mcp_auto_deploy
Allows the agent to self-configure and deploy MCP servers. Covers central config, per-agent sync, web UI visibility, registration diagnostics, and validation.
external-im-integration
Connect OpenSquad agents to external IM platforms (Feishu/Lark, QQ, Telegram). Covers plugin service setup, adapter processes, Gateway auth, workspace path fixes, and troubleshooting. Uses Feishu as the reference example.
opensquad_intro
When you need to understand how to use OpenSquad, its architectural design, or its features, load this skill to get a system overview and documentation navigation guide.