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 skills/dimetron/pi-go/bubbletea-testingnpx skills add dimetron/pi-go --skill bubbletea-testinggit clone --depth 1 https://github.com/dimetron/pi-goWhat 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.00139 | $0.03679 |
| Opus 5 | $0.00069 | $0.01840 |
| Sonnet 5 | $0.00028 | $0.00736 |
| Haiku 4.5 | $0.00014 | $0.00368 |
Grade A, and why
bubbletea-testing 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 — 501 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bubble Tea Testing
Write robust, CI-friendly tests for Bubble Tea TUI applications using a three-layer strategy: direct model unit tests, golden file view snapshots, and full-program integration tests via teatest.
Architecture overview
Bubble Tea's Elm Architecture (Init, Update, View) makes TUI apps inherently testable. Update(msg) -> (model, cmd) is a pure function of state and message — no terminal, program, or event loop needed for most tests.
Three-layer strategy:
| Layer | Coverage | Speed | Tool |
|---|---|---|---|
| 1. Direct model tests | State transitions, commands, view content | ~ms | Standard testing |
| 2. Golden file snapshots | Visual regression on View() output |
~ms | golden.RequireEqual |
| 3. Full integration | End-to-end user flows | ~seconds | teatest.NewTestModel |
Target ratio: 80% Layer 1 / 15% Layer 2 / 5% Layer 3.
Layer 1: Direct model unit tests
Constructing test messages
Build tea.Msg values directly — they are plain Go structs:
// v1
qKey := tea.KeyMsg{Type: tea.KeyRunes, Runes: []rune("q")}
enter := tea.KeyMsg{Type: tea.KeyEnter}
ctrlC := tea.KeyMsg{Type: tea.KeyCtrlC}
down := tea.KeyMsg{Type: tea.KeyDown}
resize := tea.WindowSizeMsg{Width: 80, Height: 24}
// v2 renames
qKey := tea.KeyPressMsg{Type: tea.KeyRunes, Runes: []rune("q")}
click := tea.MouseClickMsg{X: 10, Y: 5, Button: tea.MouseButtonLeft}
Table-driven Update tests
The standard pattern — each case specifies initial state, message, and expected outcome:
func TestUpdate(t *testing.T) {
tests := []struct {
name string
initial model
msg tea.Msg
wantCursor int
wantQuit bool
}{
{
name: "down moves cursor",
initial: model{cursor: 0, choices: []string{"a", "b", "c"}},
msg: tea.KeyMsg{Type: tea.KeyDown},
wantCursor: 1,
},
{
name: "cursor stops at bottom",
initial: model{cursor: 2, choices: []string{"a", "b", "c"}},
msg: tea.KeyMsg{Type: tea.KeyDown},
wantCursor: 2,
},
{
name: "q triggers quit",
initial: model{},
msg: tea.KeyMsg{Type: tea.KeyRunes, Runes: []rune("q")},
wantQuit: true,
},
}
for _, tt := range tests {
t.Run(tt.name, func(t *testing.T) {
updated, cmd := tt.initial.Update(tt.msg)
m := updated.(model)
if m.cursor != tt.wantCursor {
t.Errorf("cursor = %d, want %d", m.cursor, tt.wantCursor)
}
if tt.wantQuit {
if cmd == nil {
t.Fatal("expected quit command")
}
if _, ok := cmd().(tea.QuitMsg); !ok {
t.Error("quit command did not return QuitMsg")
}
}
})
}
}
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 · 501 lines · 139 tokens per session scan A b2020f5cf807
bubbletea-testing is a skill published in the GitHub repository dimetron/pi-go (148 stars, last pushed 3d ago), licensed MIT. It adds 139 tokens to every session and 3,679 once invoked, about $0.0007 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 skills, from other repositories
use-modern-go
Use the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.
test-with-gt
Write Go test code using the gt library. Use when writing tests, creating test files, or when the user asks to add tests for Go code.
go-testing
Use when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff. Also use when a user asks to write a test for a Go function, even if they don't mention specific patterns like table-driven tests or subtests. Does…
go-test-implementation
Executable Go falsifiers. Use for a test-only change after the proof obligation, oracle, and proving layer are accepted, or when a non-routine fixture or harness must be built.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
go-specialist
Go code review specialist for VM Agent and CLI. Reviews PTY/WebSocket/JWT code, CLI command contracts, static-analysis findings, and Go idioms. Use when working in packages/vm-agent/, packages/cli/, or reviewing Go code changes.