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/1024xengineer/bytemind/bubbleteanpx skills add 1024XEngineer/bytemind --skill bubbleteagit clone --depth 1 https://github.com/1024XEngineer/bytemindWhat 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.00033 | $0.00430 |
| Opus 5 | $0.00016 | $0.00215 |
| Sonnet 5 | $0.00007 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
bubbletea 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 2d 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.
This is a copy
100% identical to bubbletea — 108 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Bubbletea Documentation
Bubbletea is a Go framework for building terminal user interfaces based on The Elm Architecture.
Key Resources
When you need to understand Bubbletea patterns or find examples:
-
Examples README - Overview of all available examples: https://github.com/charmbracelet/bubbletea/blob/main/examples/README.md
-
Examples Directory - Full source code for all examples: https://github.com/charmbracelet/bubbletea/tree/main/examples
How to Use
-
First, fetch the examples README to get an overview of available examples:
WebFetch https://github.com/charmbracelet/bubbletea/blob/main/examples/README.md -
Once you identify a relevant example, fetch its source code from the examples directory.
Common Examples to Reference
list- List component with filteringtable- Table componenttextinput- Text input handlingtextarea- Multi-line text inputviewport- Scrollable contentpaginator- Paginationspinner- Loading spinnersprogress- Progress barstabs- Tab navigationhelp- Help text/keybindings display
Core Concepts
- Model: Application state
- Update: Handles messages and returns updated model + commands
- View: Renders the model to a string
- Cmd: Side effects that produce messages
- Msg: Events that trigger updates
Related Charm Libraries
- Bubbles: Pre-built components (github.com/charmbracelet/bubbles)
- Lipgloss: Styling and layout (github.com/charmbracelet/lipgloss)
- Glamour: Markdown rendering (github.com/charmbracelet/glamour)
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.
- 2d ago First seen · 55 lines · 33 tokens per session scan A 82f4d9ca31b1
bubbletea is a skill published in the GitHub repository 1024XEngineer/bytemind (43 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 430 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to bubbletea, differing in 108 lines, and is treated as a copy.
Other skills, from other repositories
stack-trace-go-probe
Internal helper for meta-stack-trace-investigator. Use when a Go panic or stack trace needs Go-specific nil/error checks, go test reproducer guidance, and patch targets.
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…
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-continuous-integration
GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release pipelines, Docker build/push, repository security settings, and AI-driven PR review. Use when setting up or improving Go…
golang-dependency-injection
Comprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability, loose coupling, separation of concerns, lifecycle management), manual constructor injection, and DI library comparison (google/wire, uber-go/dig, uber-go/fx, samber/do). Use this skill when designing service architecture…
golang-design-patterns
Idiomatic Golang design patterns — functional options, constructor APIs, init() and global-state avoidance, enums, panic vs error decisions, resource management and lifecycle, graceful shutdown, timeouts and retries, streaming and iterators, and architecture styles (clean, hexagonal, DDD, flat). Apply when choosing…