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-hooks-apigit 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/moodle-hooks-api)<a href="https://agentmods.dev/rules/saadrahman01/claude-moodle-dev/moodle-hooks-api"><img src="https://agentmods.dev/badge/rules/saadrahman01/claude-moodle-dev/moodle-hooks-api.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 | $0.00000 | $0.01765 |
| Opus 5 | $0.00000 | $0.00882 |
| Sonnet 5 | $0.00000 | $0.00353 |
| Haiku 4.5 | $0.00000 | $0.00177 |
Grade A, and why
moodle-hooks-api 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 4d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Moodle Hooks API
Overview
Moodle 4.4 introduced a typed Hooks API (core\hook\manager) replacing the unmaintainable jungle of magic callback functions like <plugin>_extend_navigation, <plugin>_before_http_headers, <plugin>_extend_settings_navigation, etc. Hooks are real classes with typed payloads, dispatched through \core\di::get(\core\hook\manager::class). Plugins register interest via db/hooks.php.
When to Use
- Adding cross-cutting behavior triggered by core (navigation, page output, user login, course events) without monkey-patching
- Migrating a plugin off legacy magic callbacks (deprecated 4.4+, will be removed)
- Authoring a hook class in core or in a plugin that other plugins can listen to
- Writing tests for hook listeners
Skip when: the event you care about is a \core\event\* (Events 2 API — different system, used for audit/logging). Hooks are for modifying behavior; Events are for reacting to facts.
Core concepts
| Concept | Where it lives | Purpose |
|---|---|---|
| Hook class | classes/hook/<name>.php |
Typed payload, optional setters for listeners to mutate |
| Listener registration | db/hooks.php |
Maps hook class -> callback (Class::method) + priority |
| Dispatcher call | Core or plugin code | \core\di::get(\core\hook\manager::class)->dispatch(new \plugin\hook\thing(...)); |
| Listener method | Any class | Static or instance method taking the hook instance |
Listening to a core hook
db/hooks.php:
<?php
defined('MOODLE_INTERNAL') || die();
$callbacks = [
[
'hook' => \core\hook\output\before_standard_top_of_body_html_generation::class,
'callback' => \local_example\hook_listener::class . '::inject_banner',
'priority' => 100, // higher runs first
],
];
classes/hook_listener.php:
<?php
namespace local_example;
use core\hook\output\before_standard_top_of_body_html_generation as hook;
class hook_listener {
public static function inject_banner(hook $hook): void {
global $USER;
if (isguestuser() || !isloggedin()) {
return;
}
$hook->add_html('<div class="alert alert-info">Hello, ' . s($USER->firstname) . '</div>');
}
}
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.
- 4d ago First seen · 187 lines · 0 tokens per session scan A 6e568dade02b
moodle-hooks-api 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 1,765 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.
agents
Agent engineering standards — Agents (TR-SEC-003).
profile
Command: /profile - Run the profile workflow for this project.
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.