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/researchnpx skills add friedbotstudio/baseline --skill researchgit 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.00096 | $0.01542 |
| Opus 5 | $0.00048 | $0.00771 |
| Sonnet 5 | $0.00019 | $0.00308 |
| Haiku 4.5 | $0.00010 | $0.00154 |
Grade A, and why
research 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 yesterday.
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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are surfacing a small set of candidate approaches to a task, with honest tradeoffs, so the spec author can pick one. Decisions are not made here — the human reviewer decides at /spec. Your job is to lay out the option space.
Prereqs
scoutincompletedOR inexceptions.
Inputs
- The intake at
docs/intake/<slug>.md— Constraints and Acceptance criteria sections filter which approaches are viable. - The scout report at
docs/scout/<slug>.md— patterns in use, touchpoints, landmines. - The BRD at
docs/brd/<slug>.mdif present — NFR-### requirements (latency, compliance, etc.). - The existing tech stack — read
package.json,pyproject.toml,go.mod, lockfiles.
Mandatory: verify library APIs against current docs (the provider is a default)
For any library you intend to cite, verify its API against current documentation — never training recall.
The MCP server that fetches those docs is named in .claude/docs-provider.json; resolve it with readDocsProvider from .claude/skills/lib/docs-provider.mjs, which falls back to the shipped default when the pointer is absent or unreadable. Use that server's own library-resolution and documentation-fetch tools — read their names from the tool list rather than assuming a shape, because a project may point at a different provider.
Never cite an API from memory. Record the version present in the lockfile and confirm the docs match that major version. If the provider has no coverage (or the project ships none), fall back to WebFetch against the library's official docs / llms.txt and note the source. Any current-docs source satisfies the rule — the declared provider is the convenient default, not a hard requirement (seed.md §2.5).
Method
-
Retrieve prior art before deriving. Run:
node .claude/skills/research/retrieve.mjs --slug <slug> --terms "<intake topics + scout touched modules>" \ --touched '["<scout-touched path>","<scout-touched path>"]' --spec-dir docs/system 2>/dev/null
What ships with it
1 file 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.
- yesterday First seen · 97 lines · 96 tokens per session scan A 0e7fbd966823
research is a skill published in the GitHub repository friedbotstudio/baseline (11 stars, last pushed 5d ago), licensed Apache-2.0. It adds 96 tokens to every session and 1,542 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.
i18n-check
国际化完整性检查。检查翻译 key 是否缺失、硬编码文本、locale 文件一致性。.
vue-best-practices
Vue 2/3 代码规范检查。包括组件命名、Props 校验、Composition API 规范等。.
python-review
Python 遗留代码审查：bare except、SQL 注入、反序列化、密钥、调试输出.
rust-review
Rust 服务审查：panic、SQL 注入、密钥、错误吞没、遗留标记.