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/m3taz-ahmed/ai-globalsWrote 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/m3taz-ahmed/ai-globals/aizee)<a href="https://agentmods.dev/rules/m3taz-ahmed/ai-globals/aizee"><img src="https://agentmods.dev/badge/rules/m3taz-ahmed/ai-globals/aizee.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.1 | $0.00916 | $0.00916 |
| Opus 5 | $0.00458 | $0.00458 |
| Sonnet 5 | $0.00183 | $0.00183 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
aizee 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 8d 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
1 near-identical copy found in the catalogue:
- windsurfrules — 88% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aiZee — Global Bootloader
- Root: discovered via
AIZEE_ROOTenv orconfig.discover_root()(no hardcoded path). - Set
AIZEE_ROOTif not already set. UsePYTHONIOENCODING=utf-8on Windows. - This file is the canonical root pointer. All other OS files discover the root via
AIZEE_ROOTorconfig.discover_root()and are loaded relative to it.
Working Directory [DIR-01]
- Working directory: D:\server.ai ONLY. All edits go here.
- D:\server\aizee is READ-ONLY — updated only via batch script.
Cold Start
- Read
global-roles.md,global-workflow.md, andMemory.md. - Detect personas with
aizee persona detect --multiand load the returnedskills/before acting. Persona switch directive (mandatory): If the user message STARTS with a persona command —#انتحل,/انتحل,#reset,/reset,#persona,/persona,#redetect,#switch(or Arabic#شخصيات,/شخصيات,#بدّل,/بدّل,#حالة,/حالة,#مين,/مين,#معلومات,/معلومات) — strip the command token, then runaizee persona detect --multi "<remaining text>"and ADOPT the returned primary + secondary personas and load theirskills/+lords/before acting. For status commands (#حالة,/status,#مين,/معلومات) print the currently active persona set instead of acting. This makes persona adoption explicit and verifiable; never silently ignore these commands. - If the current project has
spec.md, read it before any action.
Runtime Gate
- Route every action through
runtime/kernel.py. - Use
aizee check <action> --args '{"tokens":N}'orKernel.actto validate policy + budget. - No destructive action without explicit user approval.
Context & Memory
- Detect stack from
package.json/composer.jsonand load matchingtech-stack/<pkg>-<ver>.mdonly after reading the lockfile for the exact version ([VER-01]). - If
graphify-out/graph.jsonexists, usegraphify queryorquery_graph(MCP); never raw grep. - Query Context7 MCP for external libraries/frameworks before implementation; use
aizee_mcp/aizee_server.pyfor global context. - Run
aizee memory ingestwhenrules/,tech-stack/, orworkflows/change; updateMemory.mdviaworkflows/17-memory-sync.mdafter every milestone.
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.
- 8d ago First seen · 56 lines · 916 tokens per session scan A c1c1aaf7c804
aizee is a cursor rule published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed yesterday), licensed MIT. It adds 916 tokens to every session, about $0.0046 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.