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/SaadRahman01/claude-moodle-devWrote 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/saadrahman01/claude-moodle-dev/cmd-moodle-bump-version)<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/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/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="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.00027 | $0.00412 |
| Opus 5.5 | $0.00011 | $0.00165 |
| Sonnet 5.5 | $0.00005 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
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 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
You will bump the Moodle plugin version and wire the upgrade step.
User's input: {user_input}
Steps:
- Read
version.phpof the target plugin. If path missing, ask which plugin. - 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
- Current is
- Update
$plugin->versioninversion.php. Optionally bump$plugin->releaseper semver if user indicates a breaking/feature change. - Open
db/upgrade.php(create if missing — use the template from themoodle-plugin-developmentskill). - Add a new
if ($oldversion < <newversion>) { ... upgrade_plugin_savepoint(...); }block at the END of the function (after existing blocks, beforereturn true;). - 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. - Remind the user:
- Re-export
db/install.xmlfrom the XMLDB editor (/admin/tool/xmldb/) - Run
php admin/cli/upgrade.php --non-interactive - Add an entry in
upgrade.txt - Update
CHANGELOG.mdif maintained
- Re-export
Print the diff and the upgrade command to run.
Reference the moodle-upgrade-migration skill for cross-version concerns.
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 · 30 lines · 412 tokens per session scan A d4cb1d794871
cmd-moodle-bump-version is a cursor rule published in the GitHub repository SaadRahman01/claude-moodle-dev (42 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 412 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-30.
cmd-moodle-bump-version compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| cmd-moodle-bump-versionSaadRahman01/claude-moodle-dev | Cursor rule | 42 | 4mo ago | MIT | A | 27 | Cursor |
| ecoconception-phpInstitut-du-Numerique-Responsable/skill-nr | Cursor rule | 8 | 2d ago | CC-BY-SA-4.0 | A | 524 | Cursor |
| add-landing-templateclassroomio/classroomio | Cursor rule | 1.7k | yesterday | AGPL-3.0 | A | 0 | Cursor |
| laravel-package-coding-standardsholtwood/awesome-cursorrules-zh | Cursor rule | 241 | 18d ago | MIT | A | 0 | Cursor |
| laravelsanjeed5/awesome-cursor-rules-mdc | Cursor rule | 3.6k | 5mo ago | CC0-1.0 | A | 2,628 | Cursor |
| backendshopsys/shopsys | Cursor rule | 351 | yesterday | none | A | 0 | Cursor |
| linuxAcKeskin/contexture | Cursor rule | 2 | 2d ago | MIT | A | 1,224 | Cursor |