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/atman-33/workhub/create-pull-requestnpx skills add atman-33/workhub --skill create-pull-requestgit clone --depth 1 https://github.com/atman-33/workhubWhat 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.00080 | $0.00550 |
| Opus 5 | $0.00040 | $0.00275 |
| Sonnet 5 | $0.00016 | $0.00110 |
| Haiku 4.5 | $0.00008 | $0.00055 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request
Creates reviewer-friendly PR drafts for a repository selected from the active workspace's registered projects.
Quick start
- Pick the target repository using this order: a repository already resolved by a calling workflow; otherwise the repo named by the user; otherwise the repo owning the current file if it is unambiguous; otherwise a repository already surfaced in the current session's context (e.g. a registered-project list); otherwise ask one narrow question. Never assume a specific harness config file layout — it can change independently of this skill.
- Run git and gh commands in the target repository root, not in the workspace working directory.
- Save generated analysis and PR body files only under this skill's own
.tmp/directory (resolve this skill's actual base directory at runtime; never write into the workspace working directory or the target repository). - Draft first and ask for approval before creating or updating the PR, unless the user explicitly asked for immediate creation.
Workflow
- Resolve the target repository path from the active context.
- Use
Push-Location/Pop-Locationor an equivalent directory stack when switching into the target repository. - Run
scripts/analyze_changes.mjsfrom the target repository to produce the analysis JSON. - Choose the PR template from
assets/templates/based on branch intent, then runscripts/generate_pr_body.mjs. - Run
scripts/quality_checks.mjsbefore presenting or creating the PR. - Present the draft and warnings to the user, or create or update the PR immediately if the user explicitly asked for that fast path.
Guardrails
- Never run git or gh against the workspace working directory (e.g. the workhub vault) unless the PR is intentionally for that repository itself.
- Keep all temporary PR artifacts inside
.tmp/in this skill directory. - Treat a requested output language as binding for the final PR title and body.
- Preserve issue references, but only emit closing keywords when the PR targets the repository default branch.
- See REFERENCE.md for the full workflow, PowerShell examples, and error handling.
What ships with it
12 files 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.
- .gitignore 107 B
- assets/templates/pr-template-bugfix-ja.md 519 B
- assets/templates/pr-template-bugfix.md 570 B
- assets/templates/pr-template-docs-ja.md 442 B
- assets/templates/pr-template-docs.md 437 B
- assets/templates/pr-template-feature-ja.md 593 B
- assets/templates/pr-template-feature.md 591 B
- REFERENCE.md 6.5 KB
- references/pr-best-practices.md 5.5 KB
- scripts/analyze_changes.mjs 18 KB runs code
- scripts/generate_pr_body.mjs 16 KB runs code
- scripts/quality_checks.mjs 7.1 KB runs code
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 · 34 lines · 80 tokens per session scan A e8a5f77d51fb
create-pull-request is a skill published in the GitHub repository atman-33/workhub (2 stars, last pushed 3d ago), licensed MIT. It adds 80 tokens to every session and 550 once invoked, about $0.0004 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
readmd-localization
Use when translating or reviewing ReadMD interface strings for a target locale.
readmd-polish
Use when Markdown prose needs natural, precise editorial polishing without changing its meaning or structure.
readmd-translate
Use when a Markdown document must be translated accurately while preserving its technical structure.
aetox-translate
แปลเอกสารที่พลาดแล้วแพง - สัญญา งานราชการ เอกสารเผยแพร่ต่อสาธารณะ ศัพท์เฉพาะทาง ชื่อคน/องค์กร อ่านตัวนี้เมื่องานแปลมีอะไรมากกว่า "อ่านรู้เรื่องพอ" และความผิดพลาดจะไปโผล่ต่อหน้าคนอื่น ไม่ใช่กฎเรื่องความยาวเอกสาร.
career-changer-translator
Translate skills from one industry to another, identify transferable skills.
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…