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/eliornl/rolemule/landing-pagegit 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/landing-page)<a href="https://agentmods.dev/rules/eliornl/rolemule/landing-page"><img src="https://agentmods.dev/badge/rules/eliornl/rolemule/landing-page.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.00013 | $0.02419 |
| Opus 5 | $0.00006 | $0.01210 |
| Sonnet 5 | $0.00003 | $0.00484 |
| Haiku 4.5 | $0.00001 | $0.00242 |
Grade A, and why
landing-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 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Page
The landing page lives at ui/index.html and uses ui/static/css/landing.css + ui/src/pages/landing.ts (bundled as landing.js).
Page Sections (in order)
| Section | ID / Class | Notes |
|---|---|---|
| Hero | .hero-section |
Tagline One mule for every role. + 4-step explainer; paste / PDF·TXT·DOCX / extension |
| ↓ section arrow | .section-arrow.section-arrow--hero |
Hero → tech-bar |
| Tech Bar | .section-tech-bar |
Built-with tags (incl. Gemini/OpenAI/Anthropic/Ollama) + GitHub link to eliornl/rolemule |
| ↓ section arrow | .section-arrow |
Between each subsequent section pair |
| Problem | #problem .section-problem |
~150-application stat + time comparison cards |
| Features | #features .section-features |
Label Workflow Agents; 5 pipeline agents (.features-grid) |
| On Demand | #after-apply .section-after-apply |
Label On-Demand Agents; Optimize CV, Interview Prep, Mock Session, Hiring Outreach |
| Chrome Extension | #extension .section-extension |
Analyze This Job + Match Form To Profile + extract bullets |
| Career Tools | #tools .section-tools |
6 tool cards in Bootstrap rows |
| CLI | #cli .section-cli |
Slim strip: rolemule install + example commands (.cli-strip) |
| Screenshot Showcase | #example .section-example |
App screenshots — 10 tabs (workflow + Optimize CV / Interview / Mock Session / Outreach) |
| Pricing / CTA | #pricing .section-pricing |
Multi-provider BYOK copy; CTA → /auth/register (“Get Started Free”) |
Nav (navbar_landing.html): Why RoleMule · Workflow · On Demand · Extension · Career Tools · CLI · Example · Pricing.
Inter-Section Scroll Hints
A <div class="section-arrow"> sits between every pair of adjacent sections. It contains an anchor linking to the next section's ID with a fas fa-chevron-down icon.
<div class="section-arrow">
<a href="#problem" aria-label="Scroll to next section">
<i class="fas fa-chevron-down"></i>
</a>
</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.
- 3d ago First seen · 245 lines · 13 tokens per session scan A ff90b34ad596
landing-page is a cursor rule published in the GitHub repository eliornl/rolemule (37 stars, last pushed 4d ago), licensed MIT. It adds 13 tokens to every session and 2,419 once invoked, about $0.0001 per session on Opus 5. 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
product-manager
Holistic product leader who owns the full product lifecycle — from discovery and strategy through roadmap, stakeholder alignment, go-to-market, and outcome measurement. Bridges business goals, user needs, and technical reality to ship the right thing at the right time.
api-tester
Expert API testing specialist focused on comprehensive API validation, performance testing, and quality assurance across all systems and third-party integrations.
developer-advocate
Expert developer advocate specializing in building developer communities, creating compelling technical content, optimizing developer experience (DX), and driving platform adoption through authentic engineering engagement. Bridges product and engineering teams with external developers.
architectural-and-structural-rules
The project follows a layered architecture with clear separation of concerns.
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.