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/dasomel/oh-my-cursorWrote 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/dasomel/oh-my-cursor/release)<a href="https://agentmods.dev/rules/dasomel/oh-my-cursor/release"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/release/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/dasomel/oh-my-cursor/release"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/release.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.00013 | $0.00530 |
| Opus 5.5 | $0.00005 | $0.00212 |
| Sonnet 5.5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
release 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 2mo 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
Release Workflow
Structured release process for versioning, changelog generation, and git tagging.
Triggers
- "release", "bump version", "create release", "changelog"
Protocol
Step 1: Analyze Changes (Explorer Role)
Switching to Explorer role.
1. git log --oneline {last-tag}..HEAD → list all commits since last release
2. Categorize commits by type (feat, fix, docs, refactor, etc.)
3. Identify breaking changes
4. Determine version bump: major | minor | patch
Version Bump Rules
| Change Type | Bump | Example |
|---|---|---|
| Breaking change | major | Removing API endpoint |
| New feature | minor | Adding new command |
| Bug fix | patch | Fixing existing behavior |
| Docs/refactor only | patch | README updates |
Step 2: Generate Changelog (Writer Role)
Switching to Writer role.
Update CHANGELOG.md with:
## [X.Y.Z] - YYYY-MM-DD
### Added
- feat: description (#PR)
### Fixed
- fix: description (#PR)
### Changed
- refactor: description (#PR)
### Breaking Changes
- BREAKING: description
Step 3: Bump Version (Executor Role)
Switching to Executor role.
1. Update version in package.json
2. Update version in any other version references
3. Update CHANGELOG.md
4. Verify build passes with new version
Step 4: Create Release Commit (Git Master Role)
Switching to Git Master role.
1. Stage: package.json, CHANGELOG.md, and any version files
2. Commit: "chore: release vX.Y.Z"
3. Tag: git tag -a vX.Y.Z -m "Release vX.Y.Z"
4. Present for user approval before pushing
Step 5: User Approval
Release vX.Y.Z ready:
- Commits included: N
- Version bump: {type}
- Changelog: updated
Push to remote? (user must confirm)
Rules
- Never push without user approval
- Never skip changelog — every release must document changes
- Follow semver strictly — breaking changes = major bump
- Verify build before tagging — don't release broken code
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.
- 2mo ago First seen · 86 lines · 13 tokens per session scan A bb87a6049d3d
release is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (3 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 530 once invoked, about $0.0001 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-policy
Release, versioning, and signing policy for setmac.
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-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.
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.