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/arindamxd/camerax-androidWrote 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/arindamxd/camerax-android/bump-version)<a href="https://agentmods.dev/rules/arindamxd/camerax-android/bump-version"><img src="https://agentmods.dev/badge/rules/arindamxd/camerax-android/bump-version/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/arindamxd/camerax-android/bump-version"><img src="https://agentmods.dev/badge/rules/arindamxd/camerax-android/bump-version.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.00041 | $0.00564 |
| Opus 5.5 | $0.00016 | $0.00226 |
| Sonnet 5.5 | $0.00008 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
bump-version 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 25d 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
Same workflow as .agents/skills/bump-version/SKILL.md.
Bump version (Play upload)
Trigger phrases: bump version, version bump, bump the version. Run this workflow immediately. Do not ask whether to bump offset vs name unless they named major/minor/patch.
1. Bump versionCodeOffset
Same versionName (another Play upload of X.Y.Z):
- In root
build.gradle.kts, incrementext["versionCodeOffset"]by 1. versionCode=major * 10000 + minor * 100 + patch + offset(example: 1.7.0 + offset 5 → 10705).- Update
RELEASE.mdCurrent shipping target and Play Console Version lines to the newversionCode/ offset. Do not rewrite the historical “Last local verification” section as if those checks already ran on the new code.
Only bump versionMajor / versionMinor / versionPatch (and reset offset to 0) if the user explicitly asks for a new X.Y.Z.
Do not commit unless asked.
2. Changelog range (this upload vs previous)
Previous Play upload = the most recent commit whose subject is exactly version bumped before this bump (if HEAD is already that commit, use the one before it). Fallback: newest git tag (git tag --sort=-v:refname).
git log --format='%s' <previous>..HEAD
Skip subjects: version bumped, merge commits, docs-only, agent/DI/build-only churn.
3. Print Play Console notes
After the bump, reply with:
- One line:
versionName/ newversionCode/ new offset. - Raw bullets: remaining git subjects (changelog source).
- Paste-ready Play notes from
.cursor/rules/play-console-release-notes.mdcand AGENTS.md:Release name: {versionName}plus an<en-US>block. User-facing highlights only (4–6 bullets). End with a stability bullet when the range includes fixes. Do not invent features.
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.
- 25d ago First seen · 44 lines · 41 tokens per session scan A b67637f4a1bf
bump-version is a cursor rule published in the GitHub repository arindamxd/camerax-android (132 stars, last pushed 14d ago), licensed Apache-2.0. It adds 41 tokens to every session and 564 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-09-21.
Other cursor rules, from other repositories
betterdesk-release-workflow
Branch targeting (dev default) plus dev→main release workflow — issues, labels, release notes, and post-merge sync.
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.
release-checklist
What to update with each code change or version release.
bump-project-version
The user can provide version in one of three ways.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.