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/gfargo/tui-design-skill/agents-mdgit clone --depth 1 https://github.com/gfargo/tui-design-skillWrote 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/gfargo/tui-design-skill/agents-md)<a href="https://agentmods.dev/instructions/gfargo/tui-design-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/gfargo/tui-design-skill/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.00329 | $0.00329 |
| Opus 5 | $0.00164 | $0.00164 |
| Sonnet 5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
tui-design-skill 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 4d 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.
What it actually says
Repository guidance
GitHub release notes
Keep releases consistent with the existing v1.5.1 patch and v1.6.0 minor-release style.
- Title the release with the tag only:
vX.Y.Z. - Open with one sentence naming the release's purpose and line, without repeating the title.
- Use concise Markdown headings and bullets; describe shipped behavior, not the work session.
- Patch releases use
### Fixedplus only the relevant optional sections:### Release engineeringand### Evaluation. - Minor releases use
## Highlightswith descriptive###subsections. Add## Upgrade notesonly for user action and## Release verificationfor substantial validation evidence. - Omit empty sections. Link to the changelog at the immutable release tag, never
main. - End with the artifact SHA-256 and a full comparison link. Create a draft, attach and verify the exact-tag asset, then publish.
Patch template:
<One-sentence purpose for the X.Y line.>
### Fixed
- <User-visible correction.>
### Release engineering
- <Release-integrity change, when applicable.>
### Evaluation
- <Auditable evidence, when applicable.>
Asset SHA-256: `<sha256>`
See [CHANGELOG.md](https://github.com/gfargo/tui-design-skill/blob/vX.Y.Z/CHANGELOG.md) for the full change list.
**Full comparison:** https://github.com/gfargo/tui-design-skill/compare/vPREVIOUS...vX.Y.Z
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.
- 4d ago First seen · 38 lines · 329 tokens per session scan A 9a83d34ea7cc
tui-design-skill AGENTS.md is an instructions file published in the GitHub repository gfargo/tui-design-skill (26 stars, last pushed 2d ago), licensed MIT. It adds 329 tokens to every session, about $0.0016 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
docx-cli CLAUDE.md
Instructions for kklimuk/docx-cli, covering docx-cli, conventions, invariants, commands and testing.
superdesign-skill AGENTS.md
Instructions for superdesigndev/superdesign-skill, covering project agent memory, what this repo is, skill flow invariant: two entry paths, ground truth for cli behavior and plugin packaging & release.
stewie-pixel guidelines
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
vanguard-frontier-agentic copilot-instructions.md
Copilot instructions for VincentChuWaiChow/vanguard-frontier-agentic, covering vanguard frontier agentic repository instructions, what to optimize for, repo structure, rules for changes and cross-platform asset rule.
archeyes CLAUDE.md
Instructions for thisAAY/archeyes, covering archeyes — project guide, layout, design system, commands and publishing a release.
kleinanzeigen-reader CLAUDE.md
Instructions for its-me-prash/kleinanzeigen-reader, covering claude.md — kleinanzeigen-reader, what this repo is, auto-load instructions for claude code, quick command reference and fetch a listing.