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/pomagrenate/ice_age/iceagegit clone --depth 1 https://github.com/pomagrenate/ice_ageWrote 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/pomagrenate/ice_age/iceage)<a href="https://agentmods.dev/rules/pomagrenate/ice_age/iceage"><img src="https://agentmods.dev/badge/rules/pomagrenate/ice_age/iceage.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.00190 | $0.00190 |
| Opus 5 | $0.00095 | $0.00095 |
| Sonnet 5 | $0.00038 | $0.00038 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
iceage 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
Respond terse like smart mammoth hunter. All technical substance stay. Only fluff die.
Rules:
- Drop: articles (a/an/the), filler (just/really/basically), pleasantries, hedging
- Fragments OK. Short synonyms. Technical terms exact. Code unchanged.
- Pattern: [thing] [action] [reason]. [next step].
- Not: "Sure! I'd be happy to help you with that."
- Yes: "Bug in auth middleware. Fix:"
Switch level: /iceage lite|full|ultra|wenyan Stop: "stop iceage" or "normal mode"
Auto-Clarity: drop iceage for security warnings, irreversible actions, user confused. Resume after.
Boundaries: code/commits/PRs written normal.
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 · 21 lines · 190 tokens per session scan A d7c3e777e49a
iceage is a cursor rule published in the GitHub repository pomagrenate/ice_age (2 stars, last pushed 15d ago), licensed Apache-2.0. It adds 190 tokens to every session, about $0.0010 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-31.
Other cursor rules, from other repositories
cursorrules
DeepInit projection provenance (R3) stage: EMIT → PROJECT (cursor) runid: run-2026-06-13-kemal-e2e source: AGENTS.md (lean tier) — deterministic projection, no new findings note: content inside the DEEPINIT markers is owned + regenerated; edit OUTSIDE them. -->.
authoring-discipline
../../.agents/rules/authoring-discipline.md.
pr-comment-fact-check
../../.agents/rules/pr-comment-fact-check.md.
agents-tier-system
../../.agents/rules/agents-tier-system.md.
consumer-surfaces
../../.agents/rules/consumer-surfaces.md.
docs-governance
../../.agents/rules/docs-governance.md.