What is moodle-plugin-development?

Development rules for Moodle plugins. Moodle is a learning-management system with fixed plugin folders, naming rules, database upgrade files, permissions, language strings, and extension points.

Creating or changing Moodle plugins, database tables, permissions, web services, scheduled tasks, events, admin settings, and translated text.

They explain the framework conventions needed for a plugin to install, upgrade, translate, and work safely within Moodle.

moodle-plugin-development — Cursor rule for Cursor by SaadRahman01

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/saadrahman01/claude-moodle-dev/moodle-plugin-development/github.svg)](https://agentmods.dev/rules/saadrahman01/claude-moodle-dev/moodle-plugin-development)

Your own site

<a href="https://agentmods.dev/rules/saadrahman01/claude-moodle-dev/moodle-plugin-development"><img src="https://agentmods.dev/badge/rules/saadrahman01/claude-moodle-dev/moodle-plugin-development/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/saadrahman01/claude-moodle-dev/moodle-plugin-development"><img src="https://agentmods.dev/badge/rules/saadrahman01/claude-moodle-dev/moodle-plugin-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 3,247 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.03247
Opus 5.5	$0.00000	$0.01299
Sonnet 5.5	$0.00000	$0.00649
Haiku 4.5	$0.00000	$0.00325

Measured 1mo ago against content hash 1096253b36c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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/moodle-plugin-development.mdc · 276 lines

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.php after 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

Read the full file on GitHub · 276 lines

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.

1mo ago First seen · 276 lines · 0 tokens per session scan A 1096253b36c6

Subscribe to this mod's changes

moodle-plugin-development is a cursor rule published in the GitHub repository SaadRahman01/claude-moodle-dev (40 stars, last pushed 3mo 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.

Learning and teaching ai-coding-assistant claude claude-plugin edtech lms moodle

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.

classroomio/classroomio · 0 tokens

moodle-plugin-development

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Moodle Plugin Development

Overview

When to Use

Plugin Skeleton

What this file has done since we first saw it

Other cursor rules, from other repositories

add-landing-template

testing

discover-project

ponytail

angular-20

dev-standard