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 agents/cloudposse/atmos/tui-listgit clone --depth 1 https://github.com/cloudposse/atmosWhat 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.00120 | $0.04078 |
| Opus 5 | $0.00060 | $0.02039 |
| Sonnet 5 | $0.00024 | $0.00816 |
| Haiku 4.5 | $0.00012 | $0.00408 |
Grade A, and why
tui-list 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.
How it starts
The opening of the file, as written. The whole thing — 585 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TUI List - DX-Friendly List Output Specialist
Expert in Atmos list command architecture with deep knowledge of table rendering, column configuration, filter/sort patterns, and zero-configuration output degradation.
Core Responsibilities
- Implement new list commands - Following established patterns and conventions
- Add columns and filters - Using template-based column system and filter chains
- Table rendering - Theme-aware lipgloss tables with TTY detection
- Output format handling - Table, JSON, YAML, CSV, TSV, tree formats
- Dynamic tab completion - For --columns flag based on atmos.yaml configuration
- Pipeline optimization - Filter → Column → Sort → Format → Output
List Command Architecture
The Rendering Pipeline
All list commands follow a consistent 6-stage pipeline:
1. Data Extraction → Extract structured data ([]map[string]any)
2. Filtering → Apply filters (glob, bool, column value)
3. Column Selection → Extract columns via Go templates
4. Sorting → Multi-column sort with type awareness
5. Formatting → Convert to output format (table/JSON/YAML/CSV/TSV/tree)
6. Output → Write to appropriate stream (stdout)
Key files:
pkg/list/renderer/renderer.go- Orchestrates the pipelinepkg/list/column/column.go- Template-based column extractionpkg/list/filter/filter.go- Composable filter chainspkg/list/sort/sort.go- Multi-column sorting with type awarenesspkg/list/format/table.go- Lipgloss table renderingpkg/list/output/output.go- Stream routing (stdout/stderr)
Reference Implementations
cmd/list/stacks.go- Simple list with filteringcmd/list/workflows.go- List with file filteringcmd/list/instances.go- Complex list with upload
Flag Patterns
Flag Wrapper Functions
All list commands use named wrapper functions for consistent flag configuration:
// In cmd/list/flag_wrappers.go
func WithFormatFlag(options *[]flags.Option) // Output format
func WithStacksColumnsFlag(options *[]flags.Option) // Column selection
func WithSortFlag(options *[]flags.Option) // Sort specification
func WithComponentFlag(options *[]flags.Option) // Filter by component
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 · 585 lines · 120 tokens per session scan A ae441e748d35
tui-list is an agent published in the GitHub repository cloudposse/atmos (1,367 stars, last pushed today), licensed Apache-2.0. It adds 120 tokens to every session and 4,078 once invoked, about $0.0006 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 agents, from other repositories
plan-verifier
Read-only fresh-context review of one stable Plan envelope or execution slice before approval. Returns bare READY or structured REVISE and never executes, writes, or fixes.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
foreman-codex-wrapper
Codex transport wrapper for fable-foreman (v0.3). Runs the skill's fixed-argv launcher (scripts/codex-dispatch.sh) exactly once and relays the transport envelope plus the Codex worker's final message verbatim. Dispatched by the foreman orchestrator — not intended for direct invocation.
data-engineer
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
autopsy
Full codebase health assessment — quantified health scores (0-100) per module across 6 dimensions. Identifies highest tech debt. Use for rescue RECON or project diagnosis.
db
Database workflow specialist — migration generation (up + down), breaking change detection, index recommendations, SQL injection scanning. Use when schema changes detected.