Borrowing it
Nothing to install: this file belongs to standardbeagle/mcp-tui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/standardbeagle/mcp-tui/main/.claude/skills/add-command/SKILL.mdgit clone --depth 1 https://github.com/standardbeagle/mcp-tuiWrote 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/standardbeagle/mcp-tui/add-command)<a href="https://agentmods.dev/skills/standardbeagle/mcp-tui/add-command"><img src="https://agentmods.dev/badge/skills/standardbeagle/mcp-tui/add-command/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/standardbeagle/mcp-tui/add-command"><img src="https://agentmods.dev/badge/skills/standardbeagle/mcp-tui/add-command.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.00069 | $0.01629 |
| Opus 5.5 | $0.00028 | $0.00652 |
| Sonnet 5.5 | $0.00014 | $0.00326 |
| Haiku 4.5 | $0.00007 | $0.00163 |
Grade A, and why
add-command 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add CLI Subcommand
Scaffold a new CLI subcommand using cobra. Follow the side-effect isolation pattern: pure function for command logic, action objects for I/O operations.
Pre-Flight Checks
Before writing any code:
- Confirm the command name, arguments, flags, and purpose with the user
- Read the project's architecture decisions rule (
.claude/rules/architecture.md) to verify active patterns and constraints - Identify the existing command directory structure by examining neighboring commands
- Review the root command or command group this subcommand belongs to
Step 1 -- Define the Command
Create the command definition using cobra conventions.
Command Definition
- Place the command where existing commands live (e.g.,
cmd/,commands/,cli/) - Match the naming convention of neighboring commands
- Register the command with its parent command or root
Arguments and Flags
Define all inputs explicitly:
- Positional arguments: required values in a fixed order
- Required flags: named parameters that must be provided
- Optional flags: named parameters with sensible defaults
- Boolean flags: on/off toggles (default to false)
For each argument/flag, specify:
- Name (short form and long form for flags, e.g.,
-o,--output) - Type (string, int, bool, path, enum)
- Default value (for optional flags)
- Description (shown in help text)
- Validation rules (required, valid values, file must exist, etc.)
Help Text
Write clear help text following these guidelines:
- One-line description: what the command does (imperative form)
- Usage line showing required arguments and flags
- Examples section with at least two real-world invocations
- Long description if the command has non-obvious behavior
# Example help structure
command-name - Brief description of what this command does
Usage:
tool command-name [flags] <required-arg>
Examples:
tool command-name --output report.json data.csv
tool command-name --format table --verbose input/
Flags:
-o, --output string Output file path (default: stdout)
-f, --format string Output format: json, table, csv (default: json)
-v, --verbose Enable verbose output
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 · 209 lines · 69 tokens per session scan A e9e8a5e3a66d
add-command is a skill published in the GitHub repository standardbeagle/mcp-tui (12 stars, last pushed 5d ago), licensed MIT. It adds 69 tokens to every session and 1,629 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-09-28.
Other skills, from other repositories
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
agent-go-expert
Specialist subagent: Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
write-tests
Writes a unit test for one Python function. Use when the user asks for tests of existing code; not for integration tests.