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/atman-33/kiro-for-codex/agents-mdgit clone --depth 1 https://github.com/atman-33/kiro-for-codexWrote 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/atman-33/kiro-for-codex/agents-md)<a href="https://agentmods.dev/instructions/atman-33/kiro-for-codex/agents-md"><img src="https://agentmods.dev/badge/instructions/atman-33/kiro-for-codex/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 | $0.00737 | $0.00737 |
| Opus 5 | $0.00368 | $0.00368 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
kiro-for-codex 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Kiro for Codex
This file defines the agent contract and serves as the index to project guidance. It applies repo‑wide unless overridden by a nested AGENTS.md.
Steering Documents
- Use Steering as the authoritative source for product, technical, and structural guidance.
- Location:
.codex/steering/product.md,.codex/steering/tech.md,.codex/steering/structure.md. - Access: Resolve paths via
ConfigManager(e.g.,ConfigManager.getPath('steering')). Do not hardcode absolute paths. - Mutations: Treat Steering as read‑only; perform changes only via feature flows (Init/Refine/Delete), not ad‑hoc edits.
- Usage: When producing outputs, summarize applicable Steering points and cite the specific file/section; do not restate content verbatim.
Decision Precedence
- Code-level flags and constraints in "src/constants.ts"
- Steering documents under ".codex/steering/*.md"
- This AGENTS.md contract (general repository conventions)
- Generic assumptions (avoid unless explicitly allowed)
Agent Behavior Contract
- Use
CodexProviderfor CLI operations; build commands withCommandBuilder; execute viaProcessManager. Do not spawn child processes directly. - Respect feature flags and constraints in
src/constants.tsand anypackage.jsoncontributes.*gating. - Logging: Use the shared OutputChannel; log key lifecycle and error paths; avoid noisy logs.
- Error handling: Use centralized services (
ErrorHandler,RetryService); avoid ad‑hoc try/catch loops. - Performance/UX: Do not block the extension host; for long tasks use split terminals and VS Code progress notifications.
- Reference Steering for naming, boundaries, and directory layout instead of restating rules here.
Paths & I/O
- Workspace I/O: Prefer VS Code FS APIs (
vscode.workspace.fs) for read/write/create. - Path resolution: Use
ConfigManagerfor all.codex/**paths; avoid absolute paths. - Write boundaries: Only write within
.codex/**, the workspace, or VS Code storage as allowed by project rules. - Steering: Do not overwrite files under
.codex/steeringdirectly; use feature flows.
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 · 54 lines · 737 tokens per session scan A 47fad85e5dce
kiro-for-codex AGENTS.md is an instructions file published in the GitHub repository atman-33/kiro-for-codex (65 stars, last pushed 11mo ago), licensed MIT. It adds 737 tokens to every session, about $0.0037 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
kiro-for-codex-ide AGENTS.md
Instructions for atman-33/kiro-for-codex-ide, covering openspec instructions, agents contract, steering documents, decision precedence and agent behavior contract.
speckit-companion CLAUDE.md
Claude Code instructions for alfredoperez/speckit-companion, covering claude.md, where things are documented, gotchas, two extensions, two sets of docs and /releases/latest resolves across both tag namespaces.
speckit-companion copilot-instructions.md
Copilot instructions for alfredoperez/speckit-companion: For additional context about technologies to be used, project structure, shell commands, and other important information, read the current plan: specs/120-reorder-sidebar-icons/plan.md.
speckit-companion AGENTS.md
AGENTS.md instructions for alfredoperez/speckit-companion: For additional context about technologies to be used, project structure, shell commands, and other important information, read the current plan: specs/108-clarify-provider-labels/plan.md.
openspec-for-copilot AGENTS.md
Instructions for atman-33/openspec-for-copilot, a project described as: A VS Code extension that gives GitHub Copilot users a guided, spec-driven workflow using OpenSpec.
figma-annotations CLAUDE.md
Instructions for richardplg2/figma-annotations, covering figma annotations — vs code extension, architecture, key concepts, commands and websocket relay.