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/friedbotstudio/baseline/cli-copy-reviewnpx skills add friedbotstudio/baseline --skill cli-copy-reviewgit clone --depth 1 https://github.com/friedbotstudio/baselineWhat 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.00111 | $0.01736 |
| Opus 5 | $0.00056 | $0.00868 |
| Sonnet 5 | $0.00022 | $0.00347 |
| Haiku 4.5 | $0.00011 | $0.00174 |
Grade A, and why
cli-copy-review 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cli-copy-review — review user-facing CLI copy before shipping
You are reviewing the user-facing text strings in the baseline's CLI for three failure modes the maintainer wants caught before each release:
- Copy/behavior mismatch — the string promises behavior the code does not perform.
- Jargon — internal terminology leaking into end-user text.
- Missing next-action — the string reports a problem or partial result without telling the user how to address it.
This skill is a quality gate, not a phase. It sits between /memory-sync and /grant-commit when the workflow has been seeded with a Run /cli-copy-review for <slug> task by /triage. It is read-only: it surfaces findings; the maintainer addresses them in subsequent conversation turns and re-runs the skill until clean.
When to use
- The workflow's task list contains
Run /cli-copy-review for <slug>(seeded by/triagebecause the request will touch user-facing CLI surfaces). - The maintainer types
/cli-copy-reviewad hoc before shipping a release.
Inputs
Capture user-facing strings from these source files:
src/cli/tui/*.js— clack-based prompts. Every string passed toprompts.intro,prompts.outro,prompts.log.*,prompts.cancel, andprompts.select(themessagefield plus eachoptions[].labelandoptions[].hint).src/cli/*.js— domain-layer errors. Every string passed toError(...)and similar constructors that propagates to stderr via the CLI's top-level error handler. Include strings emitted viaconsole.errororprocess.stderr.writefrom non-TUI modules.bin/cli.js— top-level argparse output, help/usage text, and error formatting.
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 · 101 lines · 111 tokens per session scan A 3094a72f7b72
cli-copy-review is a skill published in the GitHub repository friedbotstudio/baseline (11 stars, last pushed 6d ago), licensed Apache-2.0. It adds 111 tokens to every session and 1,736 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 skills, from other repositories
dev-standards
Enforces development workflows, quality gates, coding standards, and release processes for the deterministic-agent-control-protocol project. Use when implementing features, fixing bugs, refactoring architecture, adding integrations, updating policies, writing tests, updating documentation, or preparing releases.
code-review-with-lsp
Code review with LSP-powered code intelligence. Uses MCP tools (diagnostics, hover, references, definition, symbols) for semantic code understanding, not just text grep.
i18n-check
国际化完整性检查。检查翻译 key 是否缺失、硬编码文本、locale 文件一致性。.
vue-best-practices
Vue 2/3 代码规范检查。包括组件命名、Props 校验、Composition API 规范等。.
rust-review
Rust 服务审查：panic、SQL 注入、密钥、错误吞没、遗留标记.
python-review
Python 遗留代码审查：bare except、SQL 注入、反序列化、密钥、调试输出.