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/eliornl/rolemuleWrote 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/eliornl/rolemule/settings-page)<a href="https://agentmods.dev/rules/eliornl/rolemule/settings-page"><img src="https://agentmods.dev/badge/rules/eliornl/rolemule/settings-page/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/rules/eliornl/rolemule/settings-page"><img src="https://agentmods.dev/badge/rules/eliornl/rolemule/settings-page.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.03235 |
| Opus 5.5 | $0.00000 | $0.01294 |
| Sonnet 5.5 | $0.00000 | $0.00647 |
| Haiku 4.5 | $0.00000 | $0.00324 |
Grade A, and why
settings-page 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.
How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Settings Page
Tab Layout
File: ui/dashboard/settings.html
| Tab label | data-section |
Section div ID | Notes |
|---|---|---|---|
| Profile | profile |
profileSection |
Edit profile link + resume upload |
| AI Setup | apiKeys |
apiKeysSection |
API key cards + model selector |
| Preferences | preferences |
preferencesSection |
Workflow preferences, auto-saves |
| Privacy | privacy |
privacySection |
Export + data deletion |
| Account | account |
accountSection |
Password section (email users only) + Danger Zone |
Tab switching is handled by showSection(sectionName) via delegated click on .settings-nav a[data-section]. No onclick attributes.
Tab switching clears the alert container — showSection() empties #alertContainer on every tab change so notifications from one tab never carry over to another.
AI Setup Tab (apiKeysSection)
Required flow: select provider (preferredProviderSelect) → PATCH preferred_provider → add BYOK for Gemini/OpenAI/Anthropic (Ollama needs no key) → optional model for the active provider.
| Card / control ID | Shown when |
|---|---|
providerSelectorCard |
Always (required pick) |
serverKeyNotice |
use_vertex_ai — Vertex admin mode; no personal key |
ollamaNotice |
preferred_provider === 'ollama' |
byokNotice |
Cloud provider selected and no stored key for that provider — hidden when no provider is selected |
userKeyNotice |
Active cloud provider has a stored key |
modelSelectorCard |
Credentials ready (key saved / Ollama) and not Vertex |
Layout: provider / BYOK / model cards use .account-card.ai-setup-card — compact header + .ai-setup-card-controls (border-top, ends right after the dropdown or key row). Icons use .account-icon--amber for provider / BYOK / model.
Saved indicator: #providerSavedIndicator / #modelSavedIndicator sit inline next to the card title (not under or inside the dropdown). Fade via .save-indicator opacity like Preferences.
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 · 246 lines · 0 tokens per session scan A 1990f40e0862
settings-page is a cursor rule published in the GitHub repository eliornl/rolemule (38 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,235 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
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.