tunacode AGENTS.md

Repository instructions for tunacode-cli, a Python command-line coding agent with a text-based user interface. They explain where the code and documentation live, how the project is organized, and which checks support safe changes.

In plain words
What is it for?
Use them when orienting yourself in the tunacode-cli repository, following its development workflow, or checking that its agent and harness documentation is current.
Why use it?
They give an agent a starting point for understanding the repository before editing it. They also document the project’s testing, linting, Git, and continuous-integration expectations.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/alchemiststudiosdotai/tunacode/agents-md
Clone the repo
git clone --depth 1 https://github.com/alchemiststudiosDOTai/tunacode

Made for: Codex, OpenCode.

Per session 1,938 This file is loaded in full into every session.
When invoked 1,938 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.01938 $0.01938
Opus 5 $0.00969 $0.00969
Sonnet 5 $0.00388 $0.00388
Haiku 4.5 $0.00194 $0.00194

Measured 2d ago against content hash 7595255e911b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

AGENTS.md · 132 lines

How it starts

The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Last Updated: 2026-07-10

Repository Orientation

  • This is tunacode-cli, a terminal AI coding agent with a Textual UI and tiny-agent tool loop.
  • Primary source package: src/tunacode/.
  • Python requirement: 3.11+ (pyproject.toml).
  • We use UV and .venv

Start Here

  • docs/modules/index.md — module layer map and reading order.
  • docs/architecture/dependencies/DEPENDENCY_LAYERS.md — generated dependency summary.
  • docs/skills/audit-harness/SKILL.md — strict harness-audit procedure; treat any mismatch or failed gate as critical and run checks manually one by one.
  • docs/modules/ui/commands.md — command model and command registration notes.
  • docs/workflows/README.md — accepted development workflows and execution guidance.
  • scripts/check_agents_freshness.py — validates this file is current.

Harness Documentation Purpose

  • HARNESS.md documents the code-quality harness for this repository.
  • It captures pre-commit, pre-push, repository rules, and CI/CD checks in one place.
  • The goal is to balance developer speed with reliability when programming with code agents.
  • Use it as the operational checklist for what runs locally vs what is enforced in CI.

Git Safety and Non-Destructive Defaults

  • Follow docs/git/practices.md for local Git workflow and safety rules.
  • Use docs/git/changelog-update.md when the task is to refresh CHANGELOG.md from recently merged PRs.
  • Before performing any Git operation (git status, git add, git commit, etc.), read docs/git/practices.md in that session.
  • Default behavior is non-destructive: never delete or clean untracked files/directories unless explicitly requested by the user.
  • If unknown files appear during checks, pause and ask before cleanup.
  • During commit-time check failures, do not make architectural/refactor decisions to force a green commit; only apply trivial lint-only fixes, otherwise stop and ask for user instruction.

Top-Level Layout

  • src/tunacode/ — application code.
  • tests/ — unit and architecture tests.
  • docs/ — module documentation and architecture artifacts.
  • scripts/ — local tooling and validation scripts.
  • .github/workflows/ — CI gates and release workflows.
  • Makefile — developer-facing command shortcuts.
  • pyproject.toml — package metadata, deps, lint/type/security settings.

Read the full file on GitHub · 132 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.

  1. 2d ago First seen · 132 lines · 1,938 tokens per session scan A 7595255e911b

Subscribe to this mod's changes

tunacode AGENTS.md is an instructions file published in the GitHub repository alchemiststudiosDOTai/tunacode (124 stars, last pushed 1mo ago), licensed MIT. It adds 1,938 tokens to every session, about $0.0097 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.