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/shigindo-inc/aikata/agents-mdgit clone --depth 1 https://github.com/shigindo-inc/aikataWrote 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/shigindo-inc/aikata/agents-md)<a href="https://agentmods.dev/instructions/shigindo-inc/aikata/agents-md"><img src="https://agentmods.dev/badge/instructions/shigindo-inc/aikata/agents-md.svg" alt="Measured on agentmods" 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.02174 | $0.02174 |
| Opus 5 | $0.01087 | $0.01087 |
| Sonnet 5 | $0.00435 | $0.00435 |
| Haiku 4.5 | $0.00217 | $0.00217 |
Grade A, and why
aikata 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 5d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions for aikata Development
You are reading the canonical source for agent behavior in this repository. Tool-specific files (
CLAUDE.md,.cursor/rules/, …), when present, are generated from this file. If they disagree, this file wins. See ADR 0002.
Human contributors: start from
CONTRIBUTING.mdfor the friendlier quick-start and PR checklist. This file is the operational source of truth and the input toaikata generate; CONTRIBUTING.md is a summary.
1. Project overview
aikata is a lightweight CLI tool that scaffolds AI-readable markdown documents for projects.
- What & Why — read SPEC.md.
- How — read ARCHITECTURE.md.
- When — read ROADMAP.md.
- Terminology — read GLOSSARY.md.
- Open design questions — read
docs/decisions/open-questions.md.
The initial design rationale lives in the canonical operational docs
listed above; pre-v0.1 planning notes are preserved in git history
(see commit ea48abf).
2. Before you start
Read in this order:
- README.md — project overview.
- This file (AGENTS.md) — operating rules.
- SPEC.md — requirements.
- ARCHITECTURE.md — technical structure.
- GLOSSARY.md — terminology.
docs/memory/— long-term memory (user preferences, project context, references). Read at leastfeedback.mdbefore non-trivial work.docs/tasks/current.md— short-term working state (not yet present; introduced with the standard preset in v0.1. Until then, surface in-flight work via PR descriptions and commit messages).
For the design rationale behind any specific decision, consult the
matching ADR under docs/adr/.
3. Navigation matrix
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.
- 5d ago First seen · 199 lines · 2,174 tokens per session scan A 34cdea5a3b2d
aikata AGENTS.md is an instructions file published in the GitHub repository shigindo-inc/aikata (2 stars, last pushed 4d ago), licensed MIT. It adds 2,174 tokens to every session, about $0.0109 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
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).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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.