What is AIMA AGENTS.md?

A repository guide for AIMA, a Go program that manages AI inference on edge devices and generates K3S deployment files.

Use it when changing AIMA code, preparing releases, updating versions, or working with its hardware detection, YAML configuration, K3S, SQLite, or MCP interfaces.

It gives coding agents the project's architecture, development branch rules, release process, and versioning conventions in one place.

How Approaching-AI/AIMA configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to Approaching-AI/AIMA. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Approaching-AI/AIMA/master/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/Approaching-AI/AIMA

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/approaching-ai/aima/agents-md/github.svg)](https://agentmods.dev/instructions/approaching-ai/aima/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/approaching-ai/aima/agents-md"><img src="https://agentmods.dev/badge/instructions/approaching-ai/aima/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/approaching-ai/aima/agents-md"><img src="https://agentmods.dev/badge/instructions/approaching-ai/aima/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 3,975 This file is loaded in full into every session.

When invoked 3,975 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.03975	$0.03975
Opus 5.5	$0.01590	$0.01590
Sonnet 5.5	$0.00795	$0.00795
Haiku 4.5	$0.00398	$0.00398

Measured 2mo ago against content hash 5d4f746df90a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

AGENTS.md · 360 lines

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 develop and feature work, currently v0.5.
Development build version — <development-line>-dev, for example v0.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> or bundle/<name>/<date>, never vX.Y.Z-*.

Read the full file on GitHub · 360 lines

Changes

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.

2mo ago First seen · 360 lines · 3,975 tokens per session scan A 5d4f746df90a

Subscribe to this mod's changes

AIMA AGENTS.md is an instructions file published in the GitHub repository Approaching-AI/AIMA (19 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 3,975 tokens to every session, about $0.0159 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-30.

Git and workflow ai-agents ai-infrastructure edge-ai inference-engine kubernetes

AIMA AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
AIMA AGENTS.mdApproaching-AI/AIMA	Instructions file	19	2mo ago	Apache-2.0	A	3,975	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

AIMA: Instructions file for Codex