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 instructions/uzyn/aimx/claude-mdgit clone --depth 1 https://github.com/uzyn/aimxWhat 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.05420 | $0.05420 |
| Opus 5 | $0.02710 | $0.02710 |
| Sonnet 5 | $0.01084 | $0.01084 |
| Haiku 4.5 | $0.00542 | $0.00542 |
Grade B, and why
aimx CLAUDE.md scanned grade B 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
cargo build --release && sudo cp target/release/aimx /usr/local/bin/ How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What is aimx
Self-hosted email for AI agents. One binary, one setup command. Built-in SMTP server handles inbound. Direct SMTP delivery for outbound. aimx handles everything: ingest to Markdown, DKIM signing, MCP server, hooks (on_receive / after_send). aimx serve is the SMTP daemon. All other commands are short-lived processes.
Build and test commands
# Build
cargo build
cargo build --release
# Install locally
cargo build --release && sudo cp target/release/aimx /usr/local/bin/
# Tests (all unit + integration)
cargo test
# Single test
cargo test test_name
cargo test -- --exact module::tests::test_name
# Lint
cargo clippy -- -D warnings
cargo fmt -- --check
# Format
cargo fmt
Verifier service (separate Rust crate)
cd services/verifier
cargo build
cargo test
cargo clippy -- -D warnings
cargo fmt -- --check
CI runs both crates independently (.github/workflows/ci.yml).
Test environment escape hatches
A handful of CLI gating points refuse to run as non-root in production. The
test suite injects an opt-in to keep the post-gate code paths exercised under
a non-root cargo test runner. Set this only from the test harness:
AIMX_TEST_SKIP_AUTHZ_CHECK=1— bypasses theauthorize()call (gatingAction::HookCrud) inaimx hooks --cmdraw-shell paths so the rest of the command (config writes, fallback hints, error formatting) stays reachable withoutsudo. Read bysrc/hooks.rsonly — mailbox CRUD authz is enforced server-side over UDS and never consults this env var. Production callers must never set this — it neutralizes the authz predicate by design.
Other test-only env vars are documented next to their read sites:
AIMX_SANDBOX_FORCE_FALLBACK (force the non-systemd-run hook executor),
AIMX_CONFIG_DIR / AIMX_DATA_DIR (redirect config + storage paths),
AIMX_TEST_MAIL_DROP (use the file-drop transport instead of MX delivery),
AIMX_INTEGRATION_SUDO=1 (opt the integration suite into the root-only
MAILBOX-CRUD branch when the test runner has sudo).
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.
- 2d ago First seen · 155 lines · 5,420 tokens per session scan B d2a5631a3e7d
aimx CLAUDE.md is an instructions file published in the GitHub repository uzyn/aimx (28 stars, last pushed 4d ago), licensed MIT. It adds 5,420 tokens to every session, about $0.0271 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
obsidian-mind CLAUDE.md
Claude Code instructions for breferrari/obsidian-mind, covering obsidian mind, skills & capabilities, custom slash commands, vault structure and obsidian cli.
obsidian-mind AGENTS.md
AGENTS.md instructions for breferrari/obsidian-mind, covering obsidian mind, hooks, commands, memory and reaching this vault from another repo.
TokenTracker AGENTS.md
AGENTS.md instructions for xiufengsun/TokenTracker, covering agent instructions and insforge backend.
parallel-code CLAUDE.md
Instructions for johannesjo/parallel-code, covering parallel code, stack, commands, project structure and conventions.
neo4j-skills AGENTS.md
Instructions for neo4j-contrib/neo4j-skills, covering writing skills for this repository, language style — write for agents, not humans, six design principles, skill.md spec (agentskills.io) and frontmatter.
ox AGENTS.md
Instructions for sageox/ox, covering human attention is the scarcest resource, what is ox?, quick start, terminology and required reviews.