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/rcanpx skills add friedbotstudio/baseline --skill rcagit 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.00061 | $0.00810 |
| Opus 5 | $0.00030 | $0.00405 |
| Sonnet 5 | $0.00012 | $0.00162 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
rca 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RCA — Root Cause Analysis
You are drafting an RCA. It is a narrative of what went wrong, why, and what will change so it doesn't recur. Unlike the other artifact skills in this workflow, RCA is not part of the linear phase chain — it's a separate document that often feeds into a bugfix intake (/triage → /intake → …).
Use an RCA when:
- A production incident occurred (outage, data corruption, security breach).
- A test that previously passed now fails intermittently and the cause is non-obvious.
- A
verifyskill verdict has beenFAILacross multiple attempts and the team needs a blameless record. - The user explicitly says "postmortem", "RCA", "incident review", or equivalent.
Don't use an RCA for: a bug reported in a ticket, a missing feature, or a normal TDD failure. Those belong in intake/spec/tdd.
Inputs
- The incident's observable facts: timeline, alerts, logs, user reports, metrics screenshots (paths or URLs).
- The commits, deploys, or config changes in the suspect window.
template.mdin this skill directory.
Steps
- Read
template.md. Every heading must appear in the output. - Assemble the Timeline from raw evidence (logs, alert history, chat transcripts, deploy log). Wall-clock times in a single timezone. Do NOT paraphrase events — record what happened.
- State the Root cause as a single sentence. If you have multiple candidate causes and cannot distinguish them from the evidence, list them under Contributing factors and put "not conclusively identified" as the Root cause. Do not guess.
- Impact must be quantified. Users affected: count or estimate with method. Duration: precise. Business impact: dollars, SLA minutes, or "none measurable" — never a vague "significant".
- Action items have owners and due dates. Unassigned action items are placeholder; delete them or assign.
- Write to
docs/rca/<slug>.md. Slug:YYYY-MM-DD-<short-name>so the file sorts chronologically in the directory. - Tell the user: "RCA drafted at
docs/rca/<slug>.md. Action items: N, owners assigned: M. If this warrants a fix, run/triagewith a bugfix description referencing this RCA."
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.
- 2d ago First seen · 43 lines · 61 tokens per session scan A e5d1285df6d6
rca is a skill published in the GitHub repository friedbotstudio/baseline (11 stars, last pushed 6d ago), licensed Apache-2.0. It adds 61 tokens to every session and 810 once invoked, about $0.0003 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 注入、密钥、错误吞没、遗留标记.