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/approaching-ai/aima/agents-mdgit clone --depth 1 https://github.com/Approaching-AI/AIMAWhat 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.03975 | $0.03975 |
| Opus 5 | $0.01988 | $0.01988 |
| Sonnet 5 | $0.00795 | $0.00795 |
| Haiku 4.5 | $0.00398 | $0.00398 |
Grade A, and why
AIMA AGENTS.md 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIMA — Development Guide
What Is This
AIMA (AI-Inference-Managed-by-AI): a Go binary that manages AI inference on edge devices. It detects hardware, resolves optimal configs from a YAML knowledge base, generates K3S Pod YAML, and exposes MCP tools for AI Agents to operate everything. This project is 100% developed by Claude Code.
Tech: Go (no CGO), K3S, HAMi, SQLite (modernc.org/sqlite), MCP (JSON-RPC 2.0), Cobra CLI, log/slog.
Design docs: design/ARCHITECTURE.md (system architecture), design/PRD.md, design/MRD.md.
Release Flow & Version Management
Current development line: v0.5. Latest product release: v0.4.0.
This project uses a develop-based release flow with a single declared development line.
The development line is recorded in internal/buildinfo/series.txt. Right now that value is v0.5.
master ──●──── tag v0.2.0 ───────────────── tag v0.2.1 ──
\ /
develop ───●──●──●──●──feature──●──●──●──●──●
\ /
feat/xxx──●
| Branch | Purpose | Merges to |
|---|---|---|
master |
Production releases only. Every product release tag is created here. | — |
develop |
Main integration branch for the current development line (v0.5). |
master (via release/*) |
feat/<name> |
New feature branch from develop. |
develop |
fix/<name> |
Bug fix branch from develop. |
develop |
docs/<name> |
Documentation-only branch from develop. |
develop |
release/<ver> |
Release preparation branch for a concrete SemVer release such as release/v0.2.1. |
master + develop |
hotfix/<ver> |
Urgent production fix from master for a concrete SemVer release. |
master + develop |
Version Taxonomy
- Product version — SemVer release tag
vMAJOR.MINOR.PATCH. Only annotated tags in this exact format count as AIMA releases. - Development line — the active train for
developand feature work, currentlyv0.5. - Development build version —
<development-line>-dev, for examplev0.5-dev. The exact commit is carried separately in build metadata. - MCP protocol version — protocol compatibility only (for example
2024-11-05), not the AIMA release number. - DB/import schema version — internal compatibility counters (
PRAGMA user_version,schema_version), never product release numbers. - Catalog/component version — upstream dependency versions stored in YAML, not AIMA release numbers.
- Asset bundle tag — must use a separate namespace such as
assets/<date>orbundle/<name>/<date>, nevervX.Y.Z-*.
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 · 360 lines · 3,975 tokens per session scan A 5d4f746df90a
AIMA AGENTS.md is an instructions file published in the GitHub repository Approaching-AI/AIMA (16 stars, last pushed 9d ago), licensed Apache-2.0. It adds 3,975 tokens to every session, about $0.0199 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-30.
Other instructions, from other repositories
timoni AGENTS.md
AGENTS.md instructions for stefanprodan/timoni, covering agents.md, what timoni is, common commands, architecture and cmd/timoni/ — cli (cobra).
telepresence AGENTS.md
Instructions for telepresenceio/telepresence, covering agents.md, project overview, git workflow, design plans and build artifacts.
nvcf AGENTS.md
Instructions for NVIDIA/nvcf, covering agents.md - guide for ai coding agents, repo layout, cross-repo and stack routing, oss snapshot hygiene and local qa and testing environment safety.
openclaw-operator CLAUDE.md
Instructions for paperclipinc/openclaw-operator, covering claude.md — openclaw kubernetes operator, project overview, commands, architecture and reconciliation rules.
siclaw AGENTS.md
Instructions for scitix/siclaw, covering siclaw project instructions, project shape, before risky edits, verification and stable boundaries.
kubara AGENTS.md
Instructions for kubara-io/kubara, covering ai agent context, scope, product intent (stable), truth hierarchy and reference map.