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/mhawthorne/gzaWrote 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/rules/mhawthorne/gza/beads)<a href="https://agentmods.dev/rules/mhawthorne/gza/beads"><img src="https://agentmods.dev/badge/rules/mhawthorne/gza/beads/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/rules/mhawthorne/gza/beads"><img src="https://agentmods.dev/badge/rules/mhawthorne/gza/beads.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.00596 | $0.00596 |
| Opus 5.5 | $0.00238 | $0.00238 |
| Sonnet 5.5 | $0.00119 | $0.00119 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
beads 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beads Issue Tracking
This project uses Beads (bd) for issue tracking.
Core Rules
- Track ALL work in bd (never use markdown TODOs or comment-based task lists)
- Use
bd readyto find available work - Use
bd createto track new issues/tasks/bugs - Treat commit, push, and Dolt remote sync as policy-controlled handoff actions
- Run
bd primefor complete workflow context (SSOT for operational commands) - Default to conservative git authority: report status and proposed commands unless the user, orchestrator, or repository profile explicitly authorizes commit/sync/push
Quick Reference
bd prime # Load complete workflow context (SSOT)
bd ready # Show issues ready to work (no blockers)
bd list --status=open # List all open issues
bd create "title" -t task -p 2 # Create new issue
bd update <id> --claim # Claim work atomically
bd unclaim <id> # Release stuck issue (agent crashed)
bd close <id> # Mark complete
bd dep add <issue> <depends-on> # Add dependency
bd dolt push # Sync with remote when authorized
Workflow
- Check for ready work:
bd ready - Claim an issue atomically:
bd update <id> --claim - Do the work
- Mark complete:
bd close <id> - Handoff: report changed files, validation, issue status, and any proposed commit/sync/push commands
Issue Types
bug- Something brokenfeature- New functionalitytask- Work item (tests, docs, refactoring)epic- Large feature with subtaskschore- Maintenance (dependencies, tooling)
Priorities
0- Critical (security, data loss, broken builds)1- High (major features, important bugs)2- Medium (default, nice-to-have)3- Low (polish, optimization)4- Backlog (future ideas)
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 · 68 lines · 596 tokens per session scan A 6b6ad52e515d
beads is a cursor rule published in the GitHub repository mhawthorne/gza (12 stars, last pushed 24d ago), licensed MIT. It adds 596 tokens to every session, about $0.0024 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-09-16.
Other cursor rules, from other repositories
apexyard
ApexYard governance bridge for Cursor. Mechanical gates load from .claude/settings.json when third-party configs are on. This file is the advisory pointer.
workflow
Git branching strategy, commit conventions, and pull request workflow.
develop-feature
When the user asks to implement a new feature end-to-end requiring planning, branch creation, implementation, testing, and PR. Use for work that goes beyond a simple fix or ad-hoc task.
commits
Commit message standards and conventions.
new-project-standard
Local adoption files are authoritative. Remote links are navigation only and must not be fetched or executed at runtime.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.