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 skills add n-n-code/n-n-code-skills --skill coding-guidance-go-tuigit clone --depth 1 https://github.com/n-n-code/n-n-code-skillsWrote 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/skills/n-n-code/n-n-code-skills/coding-guidance-go-tui)<a href="https://agentmods.dev/skills/n-n-code/n-n-code-skills/coding-guidance-go-tui"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/coding-guidance-go-tui/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.
<a href="https://agentmods.dev/skills/n-n-code/n-n-code-skills/coding-guidance-go-tui"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/coding-guidance-go-tui.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00074 | $0.02331 |
| Opus 5.5 | $0.00030 | $0.00932 |
| Sonnet 5.5 | $0.00015 | $0.00466 |
| Haiku 4.5 | $0.00007 | $0.00233 |
Grade A, and why
coding-guidance-go-tui 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 1mo 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go TUI Coding Guidance
Portable implementation, refactoring, testing, and review guidance for interactive Go terminal user interfaces built with Charmbracelet Bubble Tea, Bubbles, Lip Gloss, Huh forms embedded in Bubble Tea, and related Charm libraries.
Adjacent Skills
Use this as the default principle skill for Charmbracelet Go TUI work. Compose with:
- Workflow:
thinkingfor ambiguous decision framing,recursive-thinkingfor stress-testing,tester-mindsetfor validation strategy, andsecurityfor sensitive input, shell execution, token display, or filesystem access - Project overlays:
project-core-devfor repo-specific completion discovery and reporting when needed,project-config-and-testsfor config and deterministic tests at config or path seams, andproject-platform-diagnosefor terminal capability, piped stdio, SSH, alt-screen, shell, platform, install, or runtime smoke issues - Go depth:
coding-guidance-goonly when the non-TUI Go package design, concurrency, service boundary, profiling, or module behavior is the main risk
Use coding-guidance-go instead when the task is a non-interactive Go CLI,
standalone or one-shot Huh prompt, library, worker, service, or test change with
no terminal UI state machine.
Reference Map
Load references only when the task needs that depth:
- references/charmbracelet-patterns.md for version-specific Bubble Tea APIs, Bubbles component integration, Huh forms embedded in Bubble Tea, Lip Gloss APIs, key binding patterns, and upstream example routing
- references/tui-layout-and-production.md for layout arithmetic, responsive panels, mouse hit testing, screen/focus state machines, production polish, performance, noninteractive fallbacks, and Bubble Tea code-review false positives
When Not to Lean on This Skill
- non-Go terminal UI frameworks such as ncurses, Textual, blessed, termbox, or curses-style wrappers unless only the generic TUI UX ideas apply
- simple command-line flag parsing, one-shot command output, standalone Huh forms, or other prompt-only flows that do not maintain an interactive screen
- shell-only prompt polish with Gum, VHS, Mods, or plain shell unless the user is explicitly converting the flow into a Go Bubble Tea TUI
- web, mobile, or graphical desktop UI work; use the appropriate UI or platform guidance instead
- broad Go backend, package architecture, or performance work where Bubble Tea, Bubbles, and Lip Gloss are incidental
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 205 lines · 74 tokens per session scan A 6f2a0b755c6f
coding-guidance-go-tui is a skill published in the GitHub repository n-n-code/n-n-code-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 2,331 once invoked, about $0.0003 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-31.
Other skills, from other repositories
document-code
Apply Google Style documentation standards to Python, Go, TypeScript, and Terraform code. Use when writing or reviewing code that needs docstrings/comments/JSDoc, when asked to "document this code", "add docstrings", "follow Google Style", or when improving code documentation quality. Supports Python docstrings, Go…
test-go
Write, review, and improve Go test code for this project. Use whenever generating, reviewing, or modifying Go tests - including when invoked by the Tester agent, the /test prompt, or any test-related request. Covers table-driven tests, subtests, t.Parallel(), test helpers with t.Helper(), error assertions via…
golang-documentation
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices.…
golang-modernize
Modernize Golang code to use recent language features, standard library improvements, and idiomatic patterns. Use when reviewing Go code with old-style patterns, when encountering a deprecation warning, or when the user asks for modernization, a Go version upgrade (e.g. to Go 1.27), or a CI/tooling refresh. Not for…
golang-benchmark
Golang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with…
golang-cli
Golang CLI application development. Use when building, modifying, or reviewing a Go CLI tool — especially for command structure, flag handling, configuration layering, version embedding, exit codes, I/O patterns, signal handling, shell completion, argument validation, and CLI unit testing. Also triggers when code uses…