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/paulpham157/paul-s-cursor-rulesWrote 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/paulpham157/paul-s-cursor-rules/army-and-battle-mechanics-rule)<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/army-and-battle-mechanics-rule"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/army-and-battle-mechanics-rule/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/paulpham157/paul-s-cursor-rules/army-and-battle-mechanics-rule"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/army-and-battle-mechanics-rule.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.00276 |
| Opus 5 | $0.00000 | $0.00138 |
| Sonnet 5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
army-and-battle-mechanics-rule 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 12d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- army-and-battle-mechanics-rule — 100% identical, 0 lines differ
- army-and-battle-mechanics-rule — 100% identical, 0 lines differ
What it actually says
- There is a "battle list" that shows all the battles that have happened and stats about them.
- Armies go from level 1 to level 10 based on their funding.
- Inner squares can be developed into farms, forests, mines.
- Armies require wood, food, and metal to be created.
- Nations must pay upkeep depending on the amount of armies and developed land they have.
- Battles are resolved by the difference in army level and a RISK-esque dice roll mechanic that is affected by army level.
- Armies can build castles that are good defensively and allow for funding of armies.
- Armies can be used to conquer squares from other nations.
- Armies can be used to defend squares from other nations.
- Armies can be used to attack other nations.
- Armies can be used to attack neutral squares.
- Armies can be used to attack other nations' squares.
- Armies can be used to attack neutral squares.
- Armies can be used to attack other nations' squares.
- Armies can be used to attack neutral squares.
- Nations should start with the same amount of gold and land.
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.
- 12d ago First seen · 20 lines · 0 tokens per session scan A c29545b7f103
army-and-battle-mechanics-rule is a cursor rule published in the GitHub repository paulpham157/paul-s-cursor-rules (27 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 276 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
ascii-simulation-game-cursorrules-prompt-file
Cursor rules for ASCII simulation game development.
gamemaker-gml
GameMaker Language (GML) rules for scripts, objects, events, rooms, data structures, and performance-minded game code.
dragonruby-best-practices-cursorrules-prompt-file
Cursor rules for DragonRuby development with best practices integration.
drawscape-factorio-usage
A set of coding rules for using the drawscape_factorio Python module to turn exported entity data into SVG output. It specifies the required functions, configuration values, and JSON input.
scoring-and-ranking-rules
A set of rules for scoring and ranking entries in a game or competition. Entries advance after a win, leave the pool after a loss, and receive individual rankings.
weekly-scoring-process-pseudocode
Pseudocode for a weekly scoring process, written in Chinese, that takes game results and updates the status of entries.