tuisage: Instructions file for Codex

AGENTS.md

tuisage AGENTS.md is an instructions file for Codex, OpenCode from mgood/tuisage. It costs 1,405 tokens per session, scanned A, original, MIT.

Project instructions for TuiSage, a terminal interface that helps users build command-line commands from usage specifications. They describe the project, development process, and testing approach.

In plain words
What is it for?
Use them when developing TuiSage, especially when reviewing requirements, implementing features, writing tests, or deciding when to commit changes.
Why use it?
They give coding agents the context and rules needed to make changes that fit the project.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is mgood/tuisage's own configuration. It tells Codex and OpenCode how to work on tuisage itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything tuisage configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mgood/tuisage. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mgood/tuisage/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/mgood/tuisage

Made for: Codex, OpenCode.

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

agentmods badge for tuisage AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/mgood/tuisage/agents-md/github.svg)](https://agentmods.dev/instructions/mgood/tuisage/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/mgood/tuisage/agents-md"><img src="https://agentmods.dev/badge/instructions/mgood/tuisage/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.

agentmods 80×15 button for tuisage AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/mgood/tuisage/agents-md"><img src="https://agentmods.dev/badge/instructions/mgood/tuisage/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,405 This file is loaded in full into every session.
When invoked 1,405 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.01405 $0.01405
Opus 5.5 $0.00562 $0.00562
Sonnet 5.5 $0.00281 $0.00281
Haiku 4.5 $0.00140 $0.00140

Measured 2mo ago against content hash 4280d673d3f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tuisage 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 2mo 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 · 129 lines

How it starts

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

AGENTS.md — Development Guidelines

This file contains instructions for AI agents (and developers) working on TuiSage. It defines the development process, coding standards, testing philosophy, and workflow conventions.

Project Context

TuiSage is a terminal UI for interactively building CLI commands from usage specs. It reads .usage.kdl files and presents an interactive interface for browsing subcommands, toggling flags, filling in arguments, and producing a complete command string.

Refer to these documents for increasing levels of detail:

  • REQUIREMENTS.md — what the application should do (goals, features, user stories)
  • SPECIFICATION.md — how features should behave (UI layout, interactions, data flow)
  • IMPLEMENTATION.md — how it's built (architecture, code structure, current state)
  • README.md — user-facing guide (installation, usage, keyboard shortcuts)

Development Process

  • Commit frequently to git — Make commits after completing logical units of work (e.g., after fixing a bug, adding a feature, updating documentation). This provides a history trail to track the evolution of the project.
  • Before starting a new feature or fix, review the current state of the codebase and relevant documentation.
  • After completing work, update the living documentation (REQUIREMENTS.md, SPECIFICATION.md, IMPLEMENTATION.md, README.md) to reflect changes.
  • Start by producing or updating a plan before diving into implementation. Think through the approach, edge cases, and testing strategy.
  • Work in git branches for experimental features, but commit directly to main for incremental improvements and fixes.

Testing Philosophy

Development follows a testing-focused process. Tests are an integral part of every change.

Test-First When Possible

  • When fixing a bug, write a test that reproduces the issue first, then update the code to pass the test.
  • When adding a feature, write tests that define the expected behavior, then implement to satisfy them.
  • Tests may also be used to inspect current behavior before making modifications.

Read the full file on GitHub · 129 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. 2mo ago First seen · 129 lines · 1,405 tokens per session scan A 4280d673d3f1

Subscribe to this mod's changes

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

Related

tuisage AGENTS.md compared with instructions from other repositories

tuisage AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
tuisage AGENTS.mdmgood/tuisageInstructions file1001mo agoMITA1,405Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode