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/career-tools)<a href="https://agentmods.dev/rules/eliornl/rolemule/career-tools"><img src="https://agentmods.dev/badge/rules/eliornl/rolemule/career-tools/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/career-tools"><img src="https://agentmods.dev/badge/rules/eliornl/rolemule/career-tools.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.02974 |
| Opus 5.5 | $0.00000 | $0.01190 |
| Sonnet 5.5 | $0.00000 | $0.00595 |
| Haiku 4.5 | $0.00000 | $0.00297 |
Grade A, and why
career-tools 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 — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Career Tools
Overview
6 standalone AI-powered tools at /dashboard/tools. All require auth and support BYOK.
| Tool | Agent | Rate Limit |
|---|---|---|
| Thank You Note | ThankYouWriterAgent |
10/hour |
| Rejection Analysis | RejectionAnalyzerAgent |
10/hour |
| Reference Request | ReferenceRequestWriterAgent |
10/hour |
| Job Comparison | JobComparisonAgent |
10/hour |
| Follow-up Email | FollowUpGeneratorAgent |
10/hour |
| Salary Coach | SalaryCoachAgent |
5/hour |
API Endpoints
POST /api/v1/tools/thank-you # Thank you note
POST /api/v1/tools/rejection-analysis # Rejection analysis
POST /api/v1/tools/reference-request # Reference request
POST /api/v1/tools/job-comparison # Compare 2-3 jobs
GET /api/v1/tools/followup-stages # Available stages list
POST /api/v1/tools/followup # Follow-up email
POST /api/v1/tools/salary-coach # Salary negotiation coaching
Agent Prompt Rules — No Placeholders
Every career tool agent prompt MUST include CRITICAL WRITING RULES that explicitly prohibit bracket placeholders.
Rules to include in every agent's SYSTEM_CONTEXT and/or prompt:
- Never output
[Your Name],[Recruiter Name],[Company], or any bracket placeholders - Use first name only for greetings (e.g.,
Hi Sarah,) — fall back toHi there,orDear Hiring Team,if name unknown - Close with
Best regards,— no sender name on the closing line - Subject lines must NOT include the sender's name
# ✅ CORRECT — in SYSTEM_CONTEXT
"""
CRITICAL: Never output placeholder text like [Your Name], [Recruiter Name], [Company Name].
The output must be ready-to-send with no brackets requiring manual replacement.
"""
Output JSON Schemas (per tool)
Thank You Note (thank_you_writer.py)
{
"subject": "Thank you for the interview — [Role] at [Company]",
"body": "Hi [FirstName],\n\n...\n\nBest regards,",
"tone": "professional",
"word_count": 120
}
HTML IDs: thankYouOutput, thankYouSubject (.followup-subject), thankYouBody (.followup-body)
Copy action: data-action="copyThankYouNote" → copyThankYouNote() combines subject + body
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 · 342 lines · 0 tokens per session scan A ce463404ae8e
career-tools 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 2,974 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.