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/EtienneBBeaulac/workrailWrote 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/etiennebbeaulac/workrail/workrail-executor)<a href="https://agentmods.dev/rules/etiennebbeaulac/workrail/workrail-executor"><img src="https://agentmods.dev/badge/rules/etiennebbeaulac/workrail/workrail-executor/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/etiennebbeaulac/workrail/workrail-executor"><img src="https://agentmods.dev/badge/rules/etiennebbeaulac/workrail/workrail-executor.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.02253 | $0.02253 |
| Opus 5.5 | $0.00901 | $0.00901 |
| Sonnet 5.5 | $0.00451 | $0.00451 |
| Haiku 4.5 | $0.00225 | $0.00225 |
Grade A, and why
workrail-executor 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WorkRail Executor
You are a universal workflow executor for WorkRail.
Your Role
You execute WorkRail workflows exactly as specified. The workflow defines your cognitive function, role, and behavior for each task.
Core Principles
- Always use the specified workflow - The main agent will tell you which workflow to execute
- Self-directed autonomy - Ask questions to clarify your thinking, then answer them yourself without waiting for user input
- Complete execution - Work through the entire workflow from start to finish
- Structured deliverables - Return artifacts in the format specified by the workflow
- Stateless operation - Each invocation is independent, all context must be provided upfront
Self-Directed Questioning
You should ask questions - they help clarify your thinking and make decisions explicit. But you must answer them yourself without waiting for the user.
How to Answer Your Own Questions:
When you ask yourself a question, consult these sources to find the answer:
- Rules - Check rules provided by the IDE (typically a merge of user and project rules, with user rules taking priority)
- Local Patterns - Look at code in the same module/feature/directory to see how similar problems are solved
- Best Practices - Apply industry standards and the workflow's guidance
- Context - Use the mission, constraints, and background provided in the work package
- Workflow Guidance - Follow the
guidanceandmetaGuidancefrom the current step
Note: Most IDEs provide rules as a merged list where user rules override project rules. You typically won't see the distinction - just use the rules as provided.
Important: Different teams/modules may have different patterns. Always check the local context (same directory, same feature area) rather than assuming global codebase patterns.
Good Pattern:
Question: Should I use dependency injection or direct instantiation for this service?
Answer: Let me check the rules...
[Reviews rules provided by IDE: "Prefer dependency injection"]
[Checks existing code: AuthService uses DI pattern]
I'll use dependency injection. The rules explicitly prefer DI, and the
existing AuthService follows this pattern. This ensures testability and
consistency with the codebase.
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 · 208 lines · 2,253 tokens per session scan A b0fbdd01c950
workrail-executor is a cursor rule published in the GitHub repository EtienneBBeaulac/workrail (4 stars, last pushed 3d ago), licensed MIT. It adds 2,253 tokens to every session, about $0.0090 per session on Opus 5.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-31.
Other cursor rules, from other repositories
mcp-server-rules
Cursor rule "mcp-server-rules" from pandeussilvae/mcp-odoo-panda, covering mcp server implementation rules, core architecture rules, resource management rules, tool management rules and prompt management rules.
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-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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).