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/benallfree/vibescaleWrote 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/benallfree/vibescale/changeset)<a href="https://agentmods.dev/rules/benallfree/vibescale/changeset"><img src="https://agentmods.dev/badge/rules/benallfree/vibescale/changeset/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/benallfree/vibescale/changeset"><img src="https://agentmods.dev/badge/rules/benallfree/vibescale/changeset.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.00004 | $0.00146 |
| Opus 5.5 | $0.00002 | $0.00058 |
| Sonnet 5.5 | $0.00001 | $0.00029 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
changeset 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.
What it actually says
Please analyze the git diff between the most recent tag and HEAD (excluding bun.lock), and create or update .changeset entries to document the changes.
Key aspects to document:
- Breaking changes (major version bump)
- New features (minor version bump)
- Bug fixes and improvements (patch version)
For each distinct area of change, create a separate changeset entry that is:
- Concise but descriptive
- Focused on a single theme/area
- Lists specific improvements under each change
Please ensure the changeset entries follow the format:
'package-name': patch|minor|major
Description of changes
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 · 23 lines · 4 tokens per session scan A 93013a5f4ebc
changeset is a cursor rule published in the GitHub repository benallfree/vibescale (4 stars, last pushed 1y ago), licensed MIT. It adds 4 tokens to every session and 146 once invoked, about $0.0000 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-31.
Other cursor rules, from other repositories
changesets
Changeset format and bump rules enforced by CI.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
release-checklist
What to update with each code change or version release.
github-cli-guide
A guide on how to use the Github CLI (gh cli) especially related to creating issues via the CLI.
release-policy
Release, versioning, and signing policy for setmac.