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/mgood/tuisage/agents-mdgit clone --depth 1 https://github.com/mgood/tuisageWhat 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.01405 | $0.01405 |
| Opus 5 | $0.00702 | $0.00702 |
| Sonnet 5 | $0.00281 | $0.00281 |
| Haiku 4.5 | $0.00140 | $0.00140 |
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 3d 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 — 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.
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.
- 3d ago First seen · 129 lines · 1,405 tokens per session scan A 4280d673d3f1
tuisage AGENTS.md is an instructions file published in the GitHub repository mgood/tuisage (95 stars, last pushed 1mo ago), licensed MIT. It adds 1,405 tokens to every session, about $0.0070 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
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).
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.
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.