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/documentnpx skills add friedbotstudio/baseline --skill documentgit 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.00094 | $0.02196 |
| Opus 5 | $0.00047 | $0.01098 |
| Sonnet 5 | $0.00019 | $0.00439 |
| Haiku 4.5 | $0.00009 | $0.00220 |
Grade A, and why
document 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 3d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
document — Phase 10 orchestrator
This skill does not write docs directly. It surveys the diff, decides what kinds of doc work are needed, and delegates via the Skill tool.
| Delegate skill | Kind | Runs on |
|---|---|---|
technical-writer |
A page on a documentation surface | docs-site pages, docs/** guides — anything a reader navigates to as documentation |
prose |
Prose body — any English writing that needs humanizing | inline docs, README surface, user-facing copy, summary/narrative sections |
documentation |
Technical reference | API docs, architecture notes, operational runbooks |
technical-tutorials |
Step-by-step narrative | quickstarts, walkthroughs, code tutorials |
The key shift: prose is the sole channel for prose-shaping work. It owns the humanizer pass so every word we ship is filtered. The other two are technical specialists that produce structured reference material; when they output prose paragraphs that matter, they invoke prose themselves.
Prereq
integrate in completed (or exceptions).
When each delegate fires
technical-writer— the diff adds or changes a page on a documentation surface (a docs site, adocs/**guide). It runs the full SOP: source-gathering,technical-writing,reader-level,humanizer, then gates onmeasure.mjsandscore.mjs. Prefer it overdocumentationwhenever the deliverable is a page rather than a section of reference material.documentation— diff touches a public API, config surface, module architecture, or adds runbook-worthy operational behavior. Reference material a future engineer will look up.technical-tutorials— diff adds a feature a first-time user must learn by doing. Hands-on-learning, not lookup-reference.prose— when prose needs to be written or revised:- Narrative sections inside docs the above two skills produce.
- README surface updates.
- User-facing marketing/product copy on landing, pricing, feature pages.
- One-paragraph summaries, migration narratives, release notes.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 109 lines · 94 tokens per session scan A 30d9708ce5bc
document is a skill published in the GitHub repository friedbotstudio/baseline (11 stars, last pushed 7d ago), licensed Apache-2.0. It adds 94 tokens to every session and 2,196 once invoked, about $0.0005 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.
vue-best-practices
Vue 2/3 代码规范检查。包括组件命名、Props 校验、Composition API 规范等。.
i18n-check
国际化完整性检查。检查翻译 key 是否缺失、硬编码文本、locale 文件一致性。.
rust-review
Rust 服务审查：panic、SQL 注入、密钥、错误吞没、遗留标记.
python-review
Python 遗留代码审查：bare except、SQL 注入、反序列化、密钥、调试输出.