cmd-moodle-bump-version

cmd-moodle-bump-version is a cursor rule for Cursor from SaadRahman01/claude-moodle-dev. It costs 27 tokens per session (412 once invoked), scanned A, original, MIT.

A Moodle plugin release updater. Moodle is a platform for managing online courses, and its plugins use version files and upgrade steps to apply changes safely.

In plain words
What is it for?
Use it when releasing a Moodle plugin update that needs a new version number and a database or data migration step.
Why use it?
It removes the manual work of increasing a plugin's version and recording database changes for Moodle upgrades.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when releasing a Moodle plugin update that needs a new version number and a database or data migration step.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/saadrahman01/claude-moodle-dev/cmd-moodle-bump-version
Install

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.

Clone the repo
git clone --depth 1 https://github.com/SaadRahman01/claude-moodle-dev

Made for: Cursor.

Wrote 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.

agentmods badge for cmd-moodle-bump-version

README.md
[![agentmods](https://agentmods.dev/badge/rules/saadrahman01/claude-moodle-dev/cmd-moodle-bump-version.svg)](https://agentmods.dev/rules/saadrahman01/claude-moodle-dev/cmd-moodle-bump-version)
Your own site
<a href="https://agentmods.dev/rules/saadrahman01/claude-moodle-dev/cmd-moodle-bump-version"><img src="https://agentmods.dev/badge/rules/saadrahman01/claude-moodle-dev/cmd-moodle-bump-version.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 412 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.00412
Opus 5 $0.00014 $0.00206
Sonnet 5 $0.00005 $0.00082
Haiku 4.5 $0.00003 $0.00041

Measured 7d ago against content hash d4cb1d794871, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

cmd-moodle-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 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.

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.

adapters/cursor/.cursor/rules/cmd-moodle-bump-version.mdc · 30 lines

What it actually says

You will bump the Moodle plugin version and wire the upgrade step.

User's input: {user_input}

Steps:

  1. Read version.php of the target plugin. If path missing, ask which plugin.
  2. Compute next version:
    • Current is YYYYMMDDXX
    • If today's date > current date portion: new version = <today>00
    • If today's date == current date portion: increment the trailing 2 digits
    • If current somehow > today: increment trailing 2 digits anyway, log warning
  3. Update $plugin->version in version.php. Optionally bump $plugin->release per semver if user indicates a breaking/feature change.
  4. Open db/upgrade.php (create if missing — use the template from the moodle-plugin-development skill).
  5. Add a new if ($oldversion < <newversion>) { ... upgrade_plugin_savepoint(...); } block at the END of the function (after existing blocks, before return true;).
  6. Inside the block, draft the schema/data change based on the reason argument or by asking the user. Use the XMLDB API ($dbman = $DB->get_manager(), field_exists, add_field, change_field_*, add_index, etc.). Always guard with *_exists() checks.
  7. Remind the user:
    • Re-export db/install.xml from the XMLDB editor (/admin/tool/xmldb/)
    • Run php admin/cli/upgrade.php --non-interactive
    • Add an entry in upgrade.txt
    • Update CHANGELOG.md if maintained

Print the diff and the upgrade command to run.

Reference the moodle-upgrade-migration skill for cross-version concerns.

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.

  1. 7d ago First seen · 30 lines · 412 tokens per session scan A d4cb1d794871

Subscribe to this mod's changes

cmd-moodle-bump-version is a cursor rule published in the GitHub repository SaadRahman01/claude-moodle-dev (36 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 412 once invoked, about $0.0001 per session on Opus 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-30.