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.
npx agentmods add rules/saadrahman01/claude-moodle-dev/moodle-plugin-developmentgit clone --depth 1 https://github.com/SaadRahman01/claude-moodle-devWhat 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 | $0.00000 | $0.03247 |
| Opus 5 | $0.00000 | $0.01623 |
| Sonnet 5 | $0.00000 | $0.00649 |
| Haiku 4.5 | $0.00000 | $0.00325 |
Grade A, and why
moodle-plugin-development 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Moodle Plugin Development
Overview
Moodle plugins follow strict frankenstyle naming and a fixed file layout. Every plugin lives under a type-specific directory (local/, mod/, blocks/, course/format/, theme/, auth/, enrol/, report/, question/type/, filter/, repository/, etc.) and is identified by <type>_<name> (e.g., local_school, mod_quiz, format_schoolgram).
Core principle: Moodle code must declare defined('MOODLE_INTERNAL') || die(); at top of every PHP file (except classes under classes/ autoloaded via PSR-4), use $DB for all DB access, use get_string() for user-facing text, and bump version.php for any DB or capability change.
When to Use
- Creating new plugin under
local/,mod/,blocks/,course/format/,theme/, etc. - Adding/modifying DB tables →
db/install.xml+db/upgrade.php - Adding capabilities →
db/access.php - Adding web services / external functions →
db/services.php+classes/external/ - Adding scheduled tasks →
db/tasks.php+classes/task/ - Adding events / observers →
db/events.php+classes/event/ - Adding admin settings page →
settings.php - Translating strings →
lang/<lang>/<component>.php - Reviewing PR for Moodle coding-style compliance
- Bumping
version.phpafter schema/capability change
Skip when: working purely on frontend AMD modules without backend changes, or non-Moodle PHP code.
Plugin Skeleton
Minimum files for a local_<name> plugin:
local/<name>/
version.php # required: component, version, requires, maturity
lang/en/local_<name>.php # required: 'pluginname' string
lib.php # optional: hooks (extend_navigation, pluginfile, etc.)
settings.php # optional: admin settings page
db/
install.xml # DB schema (edit via /admin/tool/xmldb/)
upgrade.php # versioned upgrade steps
access.php # capabilities
services.php # web service definitions
tasks.php # scheduled tasks
events.php # event observers
caches.php # cache definitions
classes/ # PSR-4: \local_<name>\foo\bar -> classes/foo/bar.php
external/ # external (web service) functions
task/ # scheduled task classes
event/ # custom events
privacy/provider.php # GDPR provider (REQUIRED)
templates/ # Mustache templates
amd/src/ # ES modules (built via grunt -> amd/build/)
tests/ # PHPUnit + Behat
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.
- 3d ago First seen · 276 lines · 0 tokens per session scan A 1096253b36c6
moodle-plugin-development is a cursor rule published in the GitHub repository SaadRahman01/claude-moodle-dev (34 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,247 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 cursor rules, from other repositories
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.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.