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/commands/saadrahman01/claude-moodle-dev/moodle-bump-version)<a href="https://agentmods.dev/commands/saadrahman01/claude-moodle-dev/moodle-bump-version"><img src="https://agentmods.dev/badge/commands/saadrahman01/claude-moodle-dev/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/commands/saadrahman01/claude-moodle-dev/moodle-bump-version"><img src="https://agentmods.dev/badge/commands/saadrahman01/claude-moodle-dev/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.00000 | $0.00399 |
| Opus 5 | $0.00000 | $0.00199 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
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 9d 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
/moodle-bump-version
Bump version.php and add an upgrade.php step for a Moodle plugin.
You will bump the Moodle plugin version and wire the upgrade step.
User's 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.
- 9d ago First seen · 30 lines · 0 tokens per session scan A ba2b0e548e0c
moodle-bump-version is a command published in the GitHub repository SaadRahman01/claude-moodle-dev (36 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 399 tokens. 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 commands, from other repositories
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
release-adr-kit
You are running the adr-kit release for version $ARGUMENTS (if empty, ask which version to release).
changelog
Generate a changelog from commits.
ship
Open a pull request for the current branch, drive it green, and merge it.
GenerateReleaseNote
Compile short, beautiful, branded PDF release notes from one or more completed stories. Pass story IDs as arguments, or run with no arguments and the agent will ask. Reads FinishQa artefacts, groups by Epic, consolidates quality gates, proposes version number from release history, and generates a compact PDF saved to…
FinishQa
Release sign-off — verifies all TC outcomes recorded, no P0/P1 defects open, drafts plain-language release notes. Transitions ADO to Done.