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.
git 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/commands/axiomantic/spellbook/polish-repo-community)<a href="https://agentmods.dev/commands/axiomantic/spellbook/polish-repo-community"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/polish-repo-community/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/commands/axiomantic/spellbook/polish-repo-community"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/polish-repo-community.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.00023 | $0.05267 |
| Opus 5 | $0.00012 | $0.02634 |
| Sonnet 5 | $0.00005 | $0.01053 |
| Haiku 4.5 | $0.00002 | $0.00527 |
Grade A, and why
polish-repo-community scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md -o CODE_OF_CONDUCT.md How it starts
The opening of the file, as written. The whole thing — 617 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Infrastructure
Invariant Principles
- Zero open issues is a red flag, not a green flag. A healthy project has visible activity.
- Issue templates should lower friction, not raise it. Welcoming, not bureaucratic.
- Dev setup must take under 10 minutes or you get zero contributors.
- "Good first issue" must be genuinely approachable, not "rewrite the parser" labeled as easy.
- Every template and guide is both functional (helps users and contributors) and performative (signals project health to visitors).
Section 1: Issue Templates
Create the .github/ISSUE_TEMPLATE/ directory with three files.
1a. Bug Report (bug_report.yml)
Use GitHub's YAML form format, not the older markdown template. Keep it short, focused, and non-intimidating.
name: Bug Report
description: Report something that is not working correctly
labels: ["bug"]
body:
- type: markdown
attributes:
value: |
Thanks for taking the time to report this. Please fill out the sections
below so we can understand and reproduce the problem.
- type: textarea
id: description
attributes:
label: What happened?
description: Describe the bug. What did you expect to happen instead?
placeholder: "I expected X to happen, but Y happened instead."
validations:
required: true
- type: textarea
id: steps
attributes:
label: Steps to reproduce
description: Minimal steps to trigger the bug.
placeholder: |
1. Install version X
2. Run this command
3. See error
validations:
required: true
- type: textarea
id: environment
attributes:
label: Environment
description: OS, language/runtime version, package version.
placeholder: |
- OS: macOS 15.2
- Python: 3.12.1
- Package version: 1.2.3
validations:
required: true
- type: textarea
id: example
attributes:
label: Minimal reproducible example
description: If possible, paste a short code snippet that triggers the bug.
render: python
validations:
required: false
- type: textarea
id: error_output
attributes:
label: Error output or traceback
description: Paste any relevant error messages or stack traces.
render: shell
validations:
required: false
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.
- 7d ago First seen · 617 lines · 23 tokens per session scan A a6dda6521da0
polish-repo-community is a command published in the GitHub repository axiomantic/spellbook (10 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 5,267 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
report-issue-with-atomic
Open an issue against the atomic-claude repo itself (bugs/feature requests with the installed config, not the user's current project).
report-issue
Open a atomic GitHub issue via gh. Bug report or feature request — auto-detect from user's description.
save
Save current work state for next session. Creates/updates .planning/ files (CHECKPOINT.md, STATE.md, settings.json) so Heimdall resumes with full context. NOT a rewind — saves forward progress. Run before closing a session or at any milestone.
status
Show current Heimdall state — project phase, active agents, quality gates, conflicts.
beads-swarm
Execute beads with parallel agent swarm (dependency-aware).
beads-loop
Execute beads iteratively until all tasks complete.