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/analytics-consent-onboarding)<a href="https://agentmods.dev/rules/eliornl/rolemule/analytics-consent-onboarding"><img src="https://agentmods.dev/badge/rules/eliornl/rolemule/analytics-consent-onboarding/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/analytics-consent-onboarding"><img src="https://agentmods.dev/badge/rules/eliornl/rolemule/analytics-consent-onboarding.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.01109 |
| Opus 5.5 | $0.00000 | $0.00444 |
| Sonnet 5.5 | $0.00000 | $0.00222 |
| Haiku 4.5 | $0.00000 | $0.00111 |
Grade A, and why
analytics-consent-onboarding 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics, Consent & Onboarding
PostHog Analytics
// Track custom events
Analytics.track('custom_event', { property: 'value' });
Analytics.trackFeature('api_key_setup', 'clicked');
// User identification (automatic on login)
Analytics.identify(userId, { email });
// Workflow events (automatic)
Analytics.trackWorkflowStarted({ inputMethod: 'url' });
Analytics.trackWorkflowCompleted({ matchScore: 0.85 });
Analytics only fires if the user has accepted analytics cookies. Events queue until consent is given.
Cookie Consent
// Check before storing non-essential data
CookieConsent.hasConsent(); // true/false — accepts analytics cookies
// Get full preferences
CookieConsent.getPreferences();
// { essential: true, functional: false, analytics: false }
// Programmatic consent
CookieConsent.acceptAll();
CookieConsent.rejectAll();
CookieConsent.savePreferences({ functional: true, analytics: true });
Cookie types:
| Type | Required | Purpose |
|---|---|---|
| Essential | Always | Auth, session, security tokens |
| Functional | Optional | User preferences, UI state |
| Analytics | Optional | PostHog event tracking |
Onboarding Tour
Onboarding.start(); // start tour
Onboarding.reset(); // reset + show again
Onboarding.skip(); // skip tour
Tour auto-shows on first dashboard visit when localStorage.onboarding_completed is missing.
Returning users: if the key is missing but GET /api/v1/applications/stats/overview shows total_applications > 0, onboarding auto-completes silently (tour state is browser-local only — without this, clearing storage or switching browsers re-shows the tour).
Tour steps (conditional) — copy lives in ui/src/onboarding/steps.ts:
- Welcome (always) — RoleMule + tagline One mule for every role.
- Install Chrome Extension (always) — Analyze This Job + Match Form To Profile + load-unpacked
- Set Up Your AI Provider (only when
needsApiKey— user lackshas_credentialsand Vertex is off) — Gemini / OpenAI / Anthropic / Ollama - Analyze Job Postings (always) — paste / PDF·TXT·DOCX / extension; five-agent workflow
- Career Tools & Beyond (always — last step, "Next" becomes "Get Started ✓") — Optimize CV, Mock Session, Outreach, Career Tools, CLI (
rolemule)
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 · 92 lines · 0 tokens per session scan A 3691630a42db
analytics-consent-onboarding is a cursor rule published in the GitHub repository eliornl/rolemule (38 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,109 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
development
Development environment setup and commands for backend services.
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.