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.svg" alt="Measured on agentmods" 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 | $0.00014 | $0.00206 |
| Sonnet 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 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.
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.
- 7d 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 (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.
Other cursor rules, from other repositories
ecoconception-php
Règles d'écoconception pour le code PHP, ORM sobre, générateurs, OPcache, connexions réutilisées.
laravel
Definitive guide for writing clean, performant, and secure Laravel applications, emphasizing modern best practices and common pitfalls.
add-landing-template
Workflow for adding a new org landing-page template (editorial, vibrant, terminal, etc.) to the ClassroomIO monorepo. Activate when the user asks to add/create/build a new landing template or theme, or hands over a design reference for a new landing visual style.
laravel-package-coding-standards
A set of coding rules for Laravel packages, with conventions for names and code across several development areas.
skill-laravel-api
Padrões Globais para Projetos Laravel API (Context Engineering).
ecoconception-java
Règles d'écoconception pour le code Java, JPA/Hibernate sobre, mémoire, batch, logs.