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 kid-sid/codex-spellbook --skill github-issuesgit clone --depth 1 https://github.com/kid-sid/codex-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/kid-sid/codex-spellbook/github-issues)<a href="https://agentmods.dev/skills/kid-sid/codex-spellbook/github-issues"><img src="https://agentmods.dev/badge/skills/kid-sid/codex-spellbook/github-issues/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/kid-sid/codex-spellbook/github-issues"><img src="https://agentmods.dev/badge/skills/kid-sid/codex-spellbook/github-issues.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.00057 | $0.03535 |
| Opus 5.5 | $0.00023 | $0.01414 |
| Sonnet 5.5 | $0.00011 | $0.00707 |
| Haiku 4.5 | $0.00006 | $0.00353 |
Grade A, and why
github-issues 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.
How it starts
The opening of the file, as written. The whole thing — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issues
Write issues that are acted on — not ignored, misrouted, or reopened for missing info.
When to Activate
- Filing a bug report, feature request, or engineering task on GitHub
- Triaging an issue and assigning severity or priority
- Using the
ghCLI to create or manage issues programmatically - Handling special cases: regressions, flaky tests, security holes, data-loss bugs
- Writing acceptance criteria or reproduction steps
- Linking issues across repositories or to pull requests
Issue Types & When to Use Each
| Type | Label | Use When | Must Include |
|---|---|---|---|
| Bug | bug |
Observed behavior differs from documented or expected | Repro steps, expected vs actual, environment |
| Regression | bug, regression |
Previously working behavior broke in a specific version | Commit/PR that introduced it, last-good version |
| Feature | enhancement |
New capability that doesn't exist yet | Problem statement, proposed solution, AC |
| Task / Chore | chore |
Non-feature engineering work (refactor, migration, upgrade) | Why now, success criteria, estimated scope |
| Performance | performance |
Measurable slowdown or resource regression | Benchmark before/after, profiling output |
| Security | (private) | Vulnerability, auth bypass, data exposure | Do NOT file publicly — use private advisory |
| Documentation | documentation |
Missing, wrong, or outdated docs | Affected page/file, what's wrong, correct behavior |
| Flaky Test | flaky, ci |
Test fails intermittently with no code change | Failure frequency, CI run links, log excerpts |
Severity × Priority Matrix
Severity = impact if it occurs. Priority = urgency to fix.
| High Priority | Low Priority | |
|---|---|---|
| High Severity | P0: fix immediately, page oncall | P1: fix this sprint |
| Low Severity | P2: schedule soon, workaround exists | P3: backlog, good first issue |
P0 triggers: data loss, auth bypass, production down, PII exposure, charge errors. P1 triggers: feature broken for >1% of users, no workaround, SLA at risk.
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 · 408 lines · 57 tokens per session scan A 0653bfd0aa10
github-issues is a skill published in the GitHub repository kid-sid/codex-spellbook (22 stars, last pushed 5mo ago), licensed MIT. It adds 57 tokens to every session and 3,535 once invoked, about $0.0002 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-30.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.