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/mgiovani/cc-arsenal/rendernpx skills add mgiovani/cc-arsenal --skill rendergit clone --depth 1 https://github.com/mgiovani/cc-arsenalWhat 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.00157 | $0.01920 |
| Opus 5 | $0.00078 | $0.00960 |
| Sonnet 5 | $0.00031 | $0.00384 |
| Haiku 4.5 | $0.00016 | $0.00192 |
Grade A, and why
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 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Render
Build a page the user can work, not a document they have to scroll. Long findings lists, requirement inventories, option matrices and step plans all lose their shape as linear markdown. This skill gives them one, and gives the user a way to answer back that survives the round trip.
Invocation forms
| Form | Behavior |
|---|---|
render <mode> [subject] |
Build that mode's page for the subject |
render /<skill> [args] |
Run the wrapped skill, then render its output in the matching mode |
render <path> |
Read an existing file and convert it to its matching mode |
render |
Show the mode table and ask which one; never pick one silently |
Modes
| Mode | The page is | Per-item verdicts |
|---|---|---|
prd |
Requirements grouped by family, the evidence behind each | keep / change / drop |
plan |
Ordered steps, their dependencies, the files each touches | approve / rework / cut |
review |
Findings by severity and file, with the code excerpt | fix / won't fix / discuss |
audit |
Whole-repo findings, filterable by area and severity | same triage as review |
compare |
Options against weighted criteria, evidence per cell | pick a winner |
brainstorm |
Idea cards, the tension each one resolves, by theme | shortlist / park / drop |
explain |
The one-line answer, the mechanism, then detail on demand | none, comments only |
map |
Module graph, data flow, entry points | none, comments only |
Each mode's contents are specified in references/<mode>.md. Load only the one
you need, and load it after the mode is settled.
Workflow
1. Resolve the mode
From the first argument:
- A mode name: use it.
- A skill name with a leading slash: run that skill first, then map its output
to a mode using the table in
references/wrapping.md. - A file path: read the file, then pick the mode its content matches. State which mode you picked and why, in one line, before building.
- Nothing: print the mode table above and ask. Do not guess.
What ships with it
14 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.
- evals/evals.json 7.4 KB
- evals/trigger-eval.json 2.1 KB
- references/audit.md 1.9 KB
- references/brainstorm.md 1.5 KB
- references/compare.md 2.0 KB
- references/diagrams.md 3.6 KB
- references/explain.md 1.8 KB
- references/feedback-loop.md 10 KB
- references/map.md 1.8 KB
- references/page-kit.md 10 KB
- references/plan.md 1.8 KB
- references/prd.md 1.7 KB
- references/review.md 2.0 KB
- references/wrapping.md 2.4 KB
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 · 165 lines · 157 tokens per session scan A b66e099bbf69
render is a skill published in the GitHub repository mgiovani/cc-arsenal (7 stars, last pushed 3d ago), licensed MIT. It adds 157 tokens to every session and 1,920 once invoked, about $0.0008 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-31.
Other skills, from other repositories
foundation-meeting-brief
Produces a private strategic preparation document for the user before a meeting that matters. Captures stakes, stakeholder positions and reads, ranked desired outcomes, key messages, anticipated questions with prepared responses, risks and tensions, specific asks, and success signals. Distinct from meeting-agenda…
deliver-prd
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.
develop-adr
Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences. Use when making technical choices that affect system architecture, technology selection, or development patterns.
define-problem-statement
Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.
software-certificate-skill
面向普通用户，从真实软件项目全自动生成中国软件著作权申请资料：一次收集登记事实，自动分析业务、选择可追溯源码、取得真实界面证据，生成申请表信息、规范黑白灰操作手册、代码前后30页或全部材料及真实 DOCX/PDF；内部验证、渲染、哈希与备份只进入系统临时运行区，项目最终仅保留正式资料。适配 Codex、Claude Code、Cursor、OpenCode、WorkBuddy、QoderWork、TraeWork 及支持 Agent Skills 或 AGENTS.md 的平台。用户提到软件著作权、软著申请资料、申请表、代码材料、操作手册或软著审查时使用。.
anydoc
Convert Word (.doc/.docx/.docm), PowerPoint (.ppt/.pps/.pot/.pptx/.pptm/.ppsx/.ppsm), Excel (.xls/.xlsx/.xlsm/.xlsb), OpenDocument (.odt/.ods/.odp), RTF, EPUB, CSV, and PDF documents to clean GitHub-Flavored Markdown locally with the Any Doc CLI (npx -y @firecrawl/[email protected]): headings, GFM tables, slide structure…