Borrowing it
Nothing to install: this file belongs to schmitthub/clawker. 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/schmitthub/clawker/main/.agents/skills/cli-output/SKILL.mdgit clone --depth 1 https://github.com/schmitthub/clawkerWrote 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/schmitthub/clawker/cli-output)<a href="https://agentmods.dev/skills/schmitthub/clawker/cli-output"><img src="https://agentmods.dev/badge/skills/schmitthub/clawker/cli-output/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/schmitthub/clawker/cli-output"><img src="https://agentmods.dev/badge/skills/schmitthub/clawker/cli-output.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.00000 | $0.11050 |
| Opus 5.5 | $0.00000 | $0.04420 |
| Sonnet 5.5 | $0.00000 | $0.02210 |
| Haiku 4.5 | $0.00000 | $0.01105 |
Grade A, and why
cli-output 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 — 1,296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cli-output
Read this reference for CLI output examples. The output rules in the Serena cli/core memory define stream placement; examples below apply those rules.
1. Core Principle
Follow GitHub CLI (gh) conventions: fmt.Fprintf with ios.ColorScheme() directly. No output wrappers, no abstraction layers — just formatted writes to the correct stream.
cs := ios.ColorScheme()
fmt.Fprintf(ios.Out, "%s Built image %s\n", cs.SuccessIcon(), cs.Bold(imageTag))
2. Stream Conventions
Base Rules
| Stream | Field | Purpose |
|---|---|---|
| stdout | ios.Out |
Data, status, success, and next steps |
| stderr | ios.ErrOut |
Warnings, errors, diagnostics, and progress |
Per output type:
- Data (tables, IDs, JSON, command results) →
ios.Out(stdout) — always - Status ("Created container X", "Removed 3 volumes") →
ios.Out(stdout) - Errors →
ios.ErrOut(stderr) — viaprintError()in Main(), or pre-printed beforeSilentError - Warnings →
ios.ErrOut(stderr) — always visible regardless of piping - Next steps →
ios.Out(stdout) - Prompts →
ios.ErrOut(stderr) — visible even when stdout is piped
With --format, formatted data goes to stdout and status/progress goes to stderr.
These base rules apply to static (non-TUI) output. Live/interactive scenarios have their own rendering strategy — see per-scenario stream rules in Section 3.
Machine-Readable Output (Format/Filter Flags)
Format/filter flags are for static list commands only (Scenario 1). They produce one-shot tabular data that users pipe, grep, or script against. Do NOT add these to live-display or live-interactive commands — streaming output has its own --progress flag.
When to add format/filter flags:
* list/* lscommands —container list,image list,volume list,network list,worktree list- Any command whose primary output is a table of resources
When NOT to add:
* build,* run,* start— these are live-display (Scenario 3) with streaming progress* inspect,* logs— single-resource detail or streaming logs, not tabular lists* remove,* prune— action commands, not data queries- Live-interactive commands (Scenario 4) — BubbleTea owns the terminal
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 · 1,296 lines · 0 tokens per session scan A 08bc2f0fd2a4
cli-output is a skill published in the GitHub repository schmitthub/clawker (58 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 11,050 tokens. 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-08.
Other skills, from other repositories
prismer-notion
Notion API + ntn CLI: pages, databases, markdown, Workers.
prismer-airtable
Airtable REST API via curl. Records CRUD, filters, upserts.
prismer-himalaya
Himalaya CLI: IMAP/SMTP email from terminal.
prismer-maps
Geocode, POIs, routes, timezones via OpenStreetMap/OSRM.
prismer-teams-meeting-pipeline
Teams meeting summaries, job replay, Graph subscriptions.
prismer-product-price-monitor
Watch product, flight, or listing prices; alert on target.