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/hashiiiii/rules-for-aiWrote 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/hashiiiii/rules-for-ai/agents)<a href="https://agentmods.dev/rules/hashiiiii/rules-for-ai/agents"><img src="https://agentmods.dev/badge/rules/hashiiiii/rules-for-ai/agents/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/hashiiiii/rules-for-ai/agents"><img src="https://agentmods.dev/badge/rules/hashiiiii/rules-for-ai/agents.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.00500 | $0.00500 |
| Opus 5.5 | $0.00200 | $0.00200 |
| Sonnet 5.5 | $0.00100 | $0.00100 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
agents 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.
What it actually says
AGENTS
- Do not optimize too early
- If a task causes difficulty, do it more frequently
- Correct small defects before they become larger defects
- Never compromise
- Never assume intentions that the user did not state
- Insert a half-width space between full-width and half-width characters
- Do not use emoji
- Prioritize comments in tests
- Write comments that explain the reason
- Do not write comments that only explain the action
- Never use mocks or stubs
Language
- Project instructions (
CLAUDE.md/AGENTS.md) take precedence over resolved locale keys - If the context contains resolved locale keys, use them
- If the context does not contain resolved locale keys, read the first existing locale file in this order:
<absolute-git-dir>/rules-for-ai/LOCALE.md<repo>/.rules-for-ai/LOCALE.md~/.config/rules-for-ai/LOCALE.md- Bundled
LOCALE.default.mdin one of these locations:$CODEX_HOME/rules-for-ai/for Codex user installations<repo>/.agents/rules-for-ai/for Codex project and local installations<repo>/.cursor/rules-for-ai/for Cursor project and local installations- The plugin root for other installations
- Get
<absolute-git-dir>withgit rev-parse --absolute-git-dir - If no locale file exists, use
en_USfor all keys
Writing
- Before you write, edit, or review English prose, always read and apply the
hashiiiii-write-enskill. - Before you write, edit, or review Japanese prose, always read and apply the
hashiiiii-write-jaskill.
Git
- Use the
hashiiiii-gitskill for Git operations
Issues
- Use the
hashiiiii-issuesskill for GitHub issue operations
Pull Requests
- Use the
hashiiiii-pull-requestskill for GitHub pull request operations
Images
- Use the
hashiiiii-imagesskill to create image assets (logos, icons, favicons, and header images)
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 Changed · +5 lines · +55 tokens per session 1ff109ba04de
- 1mo ago First seen · 52 lines · 445 tokens per session scan A 8c278b6e4c13
agents is a cursor rule published in the GitHub repository hashiiiii/rules-for-ai (10 stars, last pushed 10d ago), licensed MIT. It adds 500 tokens to every session, about $0.0020 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
lean
The smallest working change. Efficiency is not carelessness. Active during delivery in the aiops bundle; off during grill/alignment.
backend-rules
A Cursor rule named backend-rules covering backend development, project structure, technology choices, runtime environment, and main process. Cursor is a coding editor with rules that guide how an agent works in a project.
safari-automation
Patterns and best practices for automating Safari browser interactions for web UI automation and testing.
flutter-rules
You are an expert in Flutter, Dart, Riverpod, Freezed, Flutter Hooks, and Supabase.
Deep-Learning-Developer
You are an expert in deep learning, transformers, diffusion models, and LLM development, with a focus on Python libraries such as PyTorch, Diffusers, Transformers, and Gradio.
nextjs-rules
You are a Senior Front-End Developer and an Expert in ReactJS, NextJS, JavaScript, TypeScript, HTML, CSS and modern UI/UX frameworks (e.g., TailwindCSS, Shadcn, Radix). You are thoughtful, give nuanced answers, and are brilliant at reasoning. You carefully provide accurate, factual, thoughtful answers, and are a…