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/rmyndharis/aimhooman/aimhoomangit clone --depth 1 https://github.com/rmyndharis/aimhoomanWrote 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/rmyndharis/aimhooman/aimhooman)<a href="https://agentmods.dev/rules/rmyndharis/aimhooman/aimhooman"><img src="https://agentmods.dev/badge/rules/rmyndharis/aimhooman/aimhooman.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.00856 | $0.00856 |
| Opus 5 | $0.00428 | $0.00428 |
| Sonnet 5 | $0.00171 | $0.00171 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade C, and why
aimhooman scanned grade C with 1 finding 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
(`id_rsa` and files containing a private-key header), `.aws/credentials`, What it actually says
aimhooman
This repository uses aimhooman to keep AI tooling artifacts out of Git history. Its policy:
- Never stage or commit local AI session/state files. Examples include
.claude.json,.claude/session*.json,.claude/history*,.claude/todos/*,.claude/shell-snapshots/*,.claude/statsig/*,.claude/projects/*,.claude/logs/*,.codex/sessions/*,.codex/history*,.codex/log/*,.codex/logs/*,.copilot/*,.cursor/session*,.cursor/chats/*,.cursor/logs/*,.aider.*,.specstory/*,.continue/sessions/*,.playwright-mcp/*,.remember/*,.superpowers/*, and.agent/*. The examples are not exhaustive; the packagedrules/paths.jsonis the detection source of truth for these artifacts. If one is staged, unstage it and keep it out of Git instead. - Never commit secrets: a real
.env(not.env.example), private keys (id_rsaand files containing a private-key header),.aws/credentials,.claude/.credentials.json, service-account keys, or a provider API key (GitHub, GitLab, npm, Slack, Anthropic, OpenAI, Google, Stripe, Hugging Face, SendGrid). Public certificates are allowed. aimhooman does not scan for secrets — this rule is on you, and a dedicated scanner such as gitleaks is the right backstop for it. - Never add AI attribution to commit messages: no
Co-authored-bytrailer naming an AI (Claude, Copilot, Codex), no "Generated with/by " lines, no AI-service noreply emails. A commit message reads as if a human wrote it. - Write in a human voice, not an AI voice. No
delve,leverage,utilize,seamless,robust,comprehensive,underscore,foster,pivotal,myriad,tapestry,landscape; no "This PR addresses…", "adversarial self-review", "live-verified", "thoroughly tested with comprehensive examples", "in today's", "let's dive in", "in conclusion"; no bold lead-in on every bullet and no paired em-dash asides. Say what broke or what changed, pick the plain short verb, name the number, and vary sentence length. If the first line could open any PR on any repo, delete it. - Treat
AGENTS.md,CLAUDE.md,GEMINI.md, and.github/copilot-instructions.mdas review-required: they may be intentional team config, so confirm before committing them.
Project map:
src/scan.mjsandsrc/rules.mjsload rules and make policy decisions.src/hook.mjsandsrc/githooks.mjsenforce them in agent and Git hooks.src/state.mjsowns local policy state.bin/aimhooman.mjsis the CLI.tests/mirrors the production paths and includes real temporary Git repos.
Use Node.js 22.8 or newer. Before finishing a change, run:
npm run check
npm test
npm run test:coverage
aimhooman also enforces the artifact and attribution rules at commit time, so a blocked commit means a real violation to fix, not a check to bypass. The rule is simple: AI works, hoomans ship.
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 · 65 lines · 856 tokens per session scan C 7e8f73e30973
aimhooman is a cursor rule published in the GitHub repository rmyndharis/aimhooman (4 stars, last pushed 22d ago), licensed MIT. It adds 856 tokens to every session, about $0.0043 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). 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
lecture-reference-linking
Guidelines for including course materials lists and inline references when writing exam answers or documentation that references course materials.
human-writing-style
Rules for writing naturally and authentically - avoid robotic AI tone in documentation, code comments, error messages, and explanations. Write like a human colleague, not a customer service bot.
documentation
Rules for documentation structure, file naming conventions, source attribution, code comments style, and linking patterns. Ensures consistent markdown organization and neutral, professional documentation.
project-organization
Rules for organizing Electron projects with clear separation between foundational/template code and application-specific code. Template code goes in src/, app-specific code goes in src/app/.
svg-icon-centering
Guidelines for creating and editing SVG icons with properly centered content using mathematical calculations.
components
Rules for component usage - which component libraries are allowed (shadcn/ui, Aceternity, Kibo, Magic UI, etc.), reuse over recreation, table implementation standards, and component modularization for both new features and existing components.