Borrowing it
Nothing to install: this file belongs to dosco/aithy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dosco/aithy/main/AGENTS.mdgit clone --depth 1 https://github.com/dosco/aithyWrote 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/instructions/dosco/aithy/agents-md)<a href="https://agentmods.dev/instructions/dosco/aithy/agents-md"><img src="https://agentmods.dev/badge/instructions/dosco/aithy/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.
<a href="https://agentmods.dev/instructions/dosco/aithy/agents-md"><img src="https://agentmods.dev/badge/instructions/dosco/aithy/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01311 | $0.01311 |
| Opus 5.5 | $0.00524 | $0.00524 |
| Sonnet 5.5 | $0.00262 | $0.00262 |
| Haiku 4.5 | $0.00131 | $0.00131 |
Grade A, and why
aithy 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 1mo 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aithy Agent Notes
Code Organization
- Keep code clean, simple, and boring.
- Put separate subsystems in separate files and folders.
- Avoid mixed-responsibility modules. Startup wiring belongs in
src/main.ts; behavior belongs in subsystem files. - Keep files short. The repo enforces a 500-line hard limit with
bun run check:lines; prefer smaller files before getting near that limit. - Follow existing patterns before adding abstractions. Add an abstraction only when it removes real duplication or isolates a clear subsystem boundary.
- When adding or materially changing user-facing features, update
README.mdin the same change so setup, security boundaries, and product capabilities stay accurate. - After upgrading
@ax-llm/ax, manually refresh the project-local Claude skills withbunx @ax-llm/ax setup-claude. Keep this manual rather than adding Ax totrustedDependencies, and remove skill directories that the upstream CLI no longer owns.
State And Sessions
- Runtime state is stored under
~/.config/aithy/<bot id>/by default. - The packaged bot id defaults to
default. - SQLite state lives at
~/.config/aithy/<bot id>/state.db. schema_migrationsis scoped by subsystem so session and soul migrations can each start at version1without colliding.- Session history is stored in
session_items. - Processed soul data is stored in
metadataunder thesoul.mdkey askey,value, and optionalhash. - Session transcripts are durable conversation memory.
- We do not persist Ax agent runtime state across turns. Each turn builds a fresh agent from the transcript; if the agent asks a clarification, the question is recorded in the transcript and the next user message is processed as a new turn (the agent re-derives any context from history).
- Responder learning persists only a bounded Ax playbook snapshot in
metadataunderplaybook.responder(64 KiB maximum). New agents apply the cached snapshot after soul guidance; noAxAgentStateis persisted. - Ax v23 can resume a clarification from
AxAgentState, but Aithy intentionally defers that path. A future implementation would need a metadata snapshot with a short TTL and strict size cap; persisted runtime bindings can contain stale fetched pages or sandbox-dependent values, so transcript reconstruction remains the safer continuation contract for now. - Persisted sessions are logical bot sessions. Live Microsandbox VMs are process resources and are recreated after restart.
bun run debuglists SQLite tables.bun run debug <table>inspects a table, andbun run debug <table> <id>looks up a row by the table's primary lookup column.
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.
- 1mo ago First seen · 61 lines · 1,311 tokens per session scan A 5f98228bba5d
aithy AGENTS.md is an instructions file published in the GitHub repository dosco/aithy (108 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,311 tokens to every session, about $0.0052 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.