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 axiomantic/spellbook --skill creating-issues-and-pull-requestsgit clone --depth 1 https://github.com/axiomantic/spellbookWrote 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/axiomantic/spellbook/creating-issues-and-pull-requests)<a href="https://agentmods.dev/skills/axiomantic/spellbook/creating-issues-and-pull-requests"><img src="https://agentmods.dev/badge/skills/axiomantic/spellbook/creating-issues-and-pull-requests.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.1 | $0.00071 | $0.02864 |
| Opus 5 | $0.00036 | $0.01432 |
| Sonnet 5 | $0.00014 | $0.00573 |
| Haiku 4.5 | $0.00007 | $0.00286 |
Grade A, and why
creating-issues-and-pull-requests 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 3d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Issues and Pull Requests
Announce: "Using creating-issues-and-pull-requests skill to handle GitHub creation."
Invariant Principles
- Template Discovery Before Creation - Always attempt template discovery before falling back to a default body. Never skip it.
- Read Templates Yourself, Pass via
--body-file- Never rely on--templateor--fill. Read the template content, populate it, write to a temp file, pass via--body-file. - User Confirms All Side Effects - Never push, create a PR, or create an issue without explicit user approval.
- Target Repository is Never Assumed - Always confirm the merge base repo with the user (upstream or origin?).
- Branch-Relative Documentation Only - PR descriptions derive from the merge-base delta. No development history, no session narratives.
- Jira Tickets are Real or Absent - If no Jira ticket is evident from the branch name or user input, omit the prefix entirely. Never fabricate ticket numbers.
- Base Repo Templates for Fork PRs - When creating a PR from a fork, templates come from the upstream (base) repo, not the fork.
- Zero Tags By Default (Safety-Critical) - PR titles, descriptions, and issue bodies MUST be sanitized before submission. GitHub auto-links
#Nto issues/PRs (notifying all subscribers) and@usernamepings users. A stray#108in a PR description pings everyone subscribed to issue 108. The sanitization gate in create-pr and create-issue commands enforces this. - Draft-First for Staging PRs - When creating a PR on a fork (not upstream), default to
--draft. Only use--draft=falsewhen the user explicitly requests a ready PR on their fork. - Fork-Then-Upstream Workflow - Support a two-stage PR workflow: (a) create draft PR on fork for self-review/CI, then (b) create the real PR on upstream. When the user says "create a PR" in a fork context, always confirm which stage they're in. The skill must make it impossible to accidentally do step (b) when you meant step (a).
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.
- 3d ago First seen · 256 lines · 71 tokens per session scan A d6d283ad8288
creating-issues-and-pull-requests is a skill published in the GitHub repository axiomantic/spellbook (10 stars, last pushed 3d ago), licensed MIT. It adds 71 tokens to every session and 2,864 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-09-03.
Other skills, from other repositories
do
Work an increment task by task through the ledger: task next, claim, implement, commit, task done with evidence. Use when saying "implement", "start working", or "continue increment".
atomic-git-discipline
Compressed commit message and PR body generator. Cuts noise from both while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious; PR bodies state only what the diff can't show, 120 words max. Use when user says "write a commit", "commit message", "generate…
version-bump
Automate version bumping in npm monorepos with CHANGELOG promotion and PR automation.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.