Borrowing it
Nothing to install: this file belongs to friedbotstudio/baseline. 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/friedbotstudio/baseline/main/.claude/skills/spec-render/SKILL.mdgit clone --depth 1 https://github.com/friedbotstudio/baselineWrote 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/friedbotstudio/baseline/spec-render)<a href="https://agentmods.dev/skills/friedbotstudio/baseline/spec-render"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/spec-render/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/friedbotstudio/baseline/spec-render"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/spec-render.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.00693 |
| Opus 5.5 | $0.00024 | $0.00277 |
| Sonnet 5.5 | $0.00012 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
spec-render 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec-render — render a spec's diagrams for review
User-invokable only. This skill has side effects (writes SVGs and an index). Claude does not invoke it autonomously.
Invocation
/spec-render <slug> — where <slug> corresponds to docs/specs/<slug>.md.
Prerequisites
javaon PATH (JDK 8+) + the pinnedplantuml.jarat.claude/bin/plantuml.jar(fetched at install time; SHA-verified). The render script invokesjava -jar .claude/bin/plantuml.jar -tsvg ...and exits 2 with a named remedy if either dep is missing.- The spec at
docs/specs/<slug>.mdexists and passesspec_diagram_presence_guard+plantuml_syntax_guard— otherwise rendering will surface the same errors.
Steps
- Validate the slug:
docs/specs/<slug>.mdmust exist. - Run the render script:
The script:node .claude/skills/spec-render/render.mjs <slug>- Reads
docs/specs/<slug>.md. - Extracts every
plantumlfenced block in source order. - For each block: classifies it by marker (c4_context / c4_container / c4_component / sequence / class / dependency_graph / state / other), writes
docs/specs/_rendered/<slug>/<NN>_<kind>.puml, then renders to<NN>_<kind>.svg. - Writes
docs/specs/_rendered/<slug>/index.mdwith section titles and image links in order.
- Reads
- Report the output path and a short per-kind count to the user.
- If any block fails to render, surface the offending index + first line + stderr tail, and exit non-zero. Do not silently skip broken blocks.
Output
docs/specs/_rendered/<slug>/<NN>_<kind>.svg— one per diagram block.docs/specs/_rendered/<slug>/<NN>_<kind>.puml— source kept next to the SVG for easier diffs.docs/specs/_rendered/<slug>/index.md— markdown index with embedded images.
Notes
- The render directory is a build output. Add
docs/specs/_rendered/to.gitignoreif you don't want the SVGs in the repo; the PlantUML sources in the spec are the source of truth. - For offline review without Java + the pinned jar, use the
plantumlMCP server from.mcp.json— it talks to a PlantUML renderer over HTTP. This skill prefers the localjava -jarpath because it's faster, keeps renders self-contained, and uses the SHA-pinned jar (so the version a consumer renders against matches what this baseline was tested with).
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.
- 1mo ago First seen · 46 lines · 60 tokens per session scan A b8fae1fc80d3
spec-render is a skill published in the GitHub repository friedbotstudio/baseline (14 stars, last pushed 13d ago), licensed Apache-2.0. It adds 60 tokens to every session and 693 once invoked, about $0.0002 per session on Opus 5.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
investment-memo-generator
Investment memo creation combining financial analysis, document generation, and structured templates. Use when creating investment memos, pitch decks, deal summaries, or investment committee materials.
impact-report-writer
Nonprofit/NGO impact report generation with data visualization suggestions, outcome metrics, narrative structure, and program data presentation. Use when writing impact reports, annual reports, or program evaluation summaries.
codebase-documenter
Write codebase documentation: READMEs, architecture docs, getting-started guides, API docs, and code comments. Use when documenting code or making a project easier for new developers.
office-xlsx
Read, create, edit, and validate Excel workbooks, data, and formulas (.xlsx).
office-docx
Create, read, edit, and validate Word documents (.docx).
office-pptx
Create, read, edit, and validate PowerPoint presentations (.pptx).