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 commands/kid-sid/claude-spellbook/create-issuegit clone --depth 1 https://github.com/kid-sid/claude-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/commands/kid-sid/claude-spellbook/create-issue)<a href="https://agentmods.dev/commands/kid-sid/claude-spellbook/create-issue"><img src="https://agentmods.dev/badge/commands/kid-sid/claude-spellbook/create-issue.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.00000 | $0.00530 |
| Opus 5 | $0.00000 | $0.00265 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
create-issue 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create one or more GitHub issues from a description. Accepts natural language — infers titles, labels, and bodies from context.
Usage: /create-issue <description of what issues to file>
Example: /create-issue The login page crashes on Safari 17 and the password reset email has a broken link
Instructions
1. Parse the arguments
Read $ARGUMENTS. Identify how many distinct issues are described — look for "and", numbered lists, separate sentences describing separate problems. Each distinct problem becomes one issue.
For each issue, determine:
- Title: concise, imperative, ≤ 72 chars (
fix:,feat:,chore:prefix optional) - Body: reproduce steps or acceptance criteria
- Labels: pick from what exists in the repo (
gh label list) — common ones:bug,enhancement,documentation,question,good first issue,performance,security - Assignee: only if the user explicitly named someone
If arguments are empty or too vague to produce a useful title and body, ask one clarifying question before proceeding.
2. Check the repo
# Confirm gh is authenticated and repo is detected
gh auth status
gh repo view --json nameWithOwner -q .nameWithOwner
# List existing labels (pick from these, don't invent new ones)
gh label list
3. Create each issue
gh issue create \
--title "<title>" \
--body "<body>" \
--label "<label1>,<label2>"
For the body, use this template:
## Description
<what is broken or what is needed>
## Steps to reproduce / Acceptance criteria
<numbered steps for bugs; bullet list of done-criteria for features>
## Expected behaviour
<what should happen>
## Actual behaviour / Current state
<what happens now — omit for feature requests>
## Context
<browser, OS, version, env — omit if not relevant>
4. Report results
After all issues are created, print a summary table:
Created N issue(s):
| # | Title | Labels | URL |
|---|-------|--------|-----|
| 42 | fix: login crashes on Safari 17 | bug | https://github.com/... |
| 43 | fix: broken link in password reset email | bug | https://github.com/... |
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 · 74 lines · 0 tokens per session scan A a06d0e551fdd
create-issue is a command published in the GitHub repository kid-sid/claude-spellbook (187 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 530 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.