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/fullive-ai/anima/english-first-engineering-workflowgit clone --depth 1 https://github.com/Fullive-AI/AnimaWrote 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/fullive-ai/anima/english-first-engineering-workflow)<a href="https://agentmods.dev/rules/fullive-ai/anima/english-first-engineering-workflow"><img src="https://agentmods.dev/badge/rules/fullive-ai/anima/english-first-engineering-workflow.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.00274 | $0.00274 |
| Opus 5 | $0.00137 | $0.00137 |
| Sonnet 5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
English-First-Engineering-Workflow 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 4d 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.
What it actually says
Use English as the default language for all implementation work.
- Use English for all engineering artifacts and execution
- Code
- Comments
- Variable names, function names, class names
- Commit messages
- CLI commands
- Logs
- Error analysis
- Tool output
- Internal workflow notes
- Text inside diagrams, charts, screenshots, and images produced for code or documentation
- Use Chinese only when interacting with me in the following cases
- You need my decision
- You need me to review an intermediate file, draft, or result
- You need me to choose between options
- You are giving me the final summary
- Interaction rules
- Do not translate implementation steps into Chinese
- Do not write comments in Chinese
- Do not write commit messages in Chinese
- Do not put Chinese text inside code-related images or diagrams
- Keep the full development workflow in English unless you are explicitly asking for my decision or review, or providing the final summary
- Output behavior
- Implementation process: English
- Requests for my decision: Chinese
- Requests for my review: Chinese
- Final summary: Chinese
- Priority If there is any conflict:
- 中文for decision requests, review requests, and final summaries
- English for everything else in the engineering workflow
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.
- 4d ago First seen · 42 lines · 274 tokens per session scan A 23468ff9d4bd
English-First-Engineering-Workflow is a cursor rule published in the GitHub repository Fullive-AI/Anima (1,049 stars, last pushed 14d ago), licensed Apache-2.0. It adds 274 tokens to every session, about $0.0014 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
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.