Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/rules/saadrahman01/claude-moodle-dev/moodle-security-audit)<a href="https://agentmods.dev/rules/saadrahman01/claude-moodle-dev/moodle-security-audit"><img src="https://agentmods.dev/badge/rules/saadrahman01/claude-moodle-dev/moodle-security-audit.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.00000 | $0.02632 |
| Opus 5 | $0.00000 | $0.01316 |
| Sonnet 5 | $0.00000 | $0.00526 |
| Haiku 4.5 | $0.00000 | $0.00263 |
Grade A, and why
moodle-security-audit scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
$curl = new \curl(); // Moodle's curl wrapper How it starts
The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Moodle Security Audit
Overview
Moodle has framework-level protections (capability system, sesskey, $DB placeholders, output escaping) — but only if used. Most Moodle plugin CVEs come from skipping these. This skill enforces the checklist.
When to Use
- Reviewing a PR for security
- Auditing existing plugin code
- Responding to a vulnerability report
- Pre-submission review for moodle.org plugin directory
Skip when: writing new feature code (use moodle-plugin-development — it covers the basics).
Audit checklist (every entry script)
require('../../config.php'); // bootstrap
require_login(); // 1. session + cookies
$context = context_course::instance($courseid); // 2. context
$PAGE->set_context($context);
require_capability('local/example:view', $context); // 3. capability
require_sesskey(); // 4. CSRF (POST only)
$id = required_param('id', PARAM_INT); // 5. typed input
$name = optional_param('name', '', PARAM_TEXT);
Order matters. require_login before context_*::instance because login resolves $USER.
1. Authentication — require_login()
| Variant | Use |
|---|---|
require_login() |
Logged-in user, any context |
require_login($course) |
Logged-in + enrolled in course |
require_login($course, true, $cm) |
Logged-in + activity-level access |
require_admin() |
Site admin only |
require_login(null, false) |
Skips guest auto-login (rare) |
Bug: Forgetting require_login() on AJAX endpoints. AJAX still needs it — session might be valid but unauthorized.
2. Authorization — capabilities
require_capability('local/example:edit', $context);
// or for soft check:
if (!has_capability('local/example:edit', $context)) {
redirect(...);
}
Bug — IDOR (Insecure Direct Object Reference):
// BAD — checks site-level cap, but $item belongs to a course user can't access
$item = $DB->get_record('local_example_items', ['id' => $id], '*', MUST_EXIST);
require_capability('local/example:view', context_system::instance());
// GOOD — derive context from the object
$item = $DB->get_record('local_example_items', ['id' => $id], '*', MUST_EXIST);
$context = context_course::instance($item->courseid);
require_capability('local/example:view', $context);
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.
- 6d ago First seen · 289 lines · 0 tokens per session scan A 1799d506fe34
moodle-security-audit is a cursor rule published in the GitHub repository SaadRahman01/claude-moodle-dev (35 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,632 tokens. A static security scan graded it A with 1 finding (makes network calls). 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.
agents
Agent engineering standards — Agents (TR-SEC-003).
profile
Command: /profile - Run the profile workflow for this project.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.