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/apiliumcode/aingle/gemini-mdgit clone --depth 1 https://github.com/ApiliumCode/aingleWhat 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.00627 | $0.00627 |
| Opus 5 | $0.00313 | $0.00313 |
| Sonnet 5 | $0.00125 | $0.00125 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
aingle GEMINI.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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 31 lines · 627 tokens per session scan A 2cde713eaa3a
aingle GEMINI.md is an instructions file published in the GitHub repository ApiliumCode/aingle (5 stars, last pushed 8d ago), with no licence file. It adds 627 tokens to every session, about $0.0031 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 instructions, from other repositories
m_flow AGENTS.md
AGENTS.md instructions for FlowElement-xinliuyuansu/m_flow, covering m-flow — developer & agent reference, 1. repository map, extension points, 2. local development and python backend (requires python 3.10 – 3.13).
engram-mcp CLAUDE.md
Instructions for edg-l/engram-mcp, covering engram mcp, development rules, structure, key types and mcp capabilities.
vellis AGENTS.md
Instructions for volantlabs/vellis, covering agents.md, repository purpose, startup checks, installing vellis for a user and model-first component workflow.
trinity AGENTS.md
AGENTS.md instructions for trinity-tick/trinity, covering agents.md — trinity memory, trinity 记忆层实时快照（生成于 2026-08-24 15:26:38）, 活跃目标（active goals）, 最近会话（recent sessions） and 1. trinity 是什么.
pensyve copilot-instructions.md
Copilot instructions for major7apps/pensyve, covering pensyve working-memory substrate for vs code copilot, memory reflex rule, "substantive answer" means, "lesson lands" means and memory classification.
pensyve AGENTS.md
AGENTS.md instructions for major7apps/pensyve, covering pensyve — agents.md, what this repo is, start here, directory map and build & dev commands.