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/aidlc-io/aidlc/render-artifactsnpx skills add aidlc-io/aidlc --skill render-artifactsgit clone --depth 1 https://github.com/aidlc-io/aidlcWhat 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.00054 | $0.00539 |
| Opus 5 | $0.00027 | $0.00269 |
| Sonnet 5 | $0.00011 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
render-artifacts 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.
What it actually says
/render-artifacts — build annotation-ready HTML from epic artifacts
Markdown is the canonical source of every epic artifact (PRD, TECH-DESIGN, TEST-PLAN,
IMPLEMENTATION-PLAN…). The produces: paths in workspace.yaml all point at .md,
and agents/pipeline re-read .md because it is ~1.5–3× cheaper in tokens. This
command does not change that. It only produces a throwaway HTML render next to
each .md so a human can open the artifact in an annotation tool (e.g. annotron) and
comment on it.
Rule: HTML is a render, not a source. To change content, edit the .md and re-run.
Never add this step to a pipeline's produces:.
Usage
/render-artifacts <epic> — e.g. /render-artifacts EPIC-001
Steps
- Resolve the artifacts folder:
docs/epics/<epic>/artifacts. If it doesn't exist, stop and say so. - Run (zero-dep Node renderer;
markedis vendored, so justnode— no pip/python):
This renders everynode tools/md-to-html.mjs --all docs/epics/<epic>/artifacts*.mdto a sibling*.htmland rewrites cross-links between sibling artifacts (PRD.md→PRD.html), while leaving links that point outside the folder or to external URLs pointing at the canonical source. - Report the written files. Remind the user that the
.htmlfiles are throwaway annotation copies — edit the.md, not the.html, and re-run to refresh.
Committing
By default treat the HTML as local-only (throwaway). If the artifacts folder is
tracked in git and you don't want the renders committed, ensure the folder's
.gitignore contains *.html. Only commit an .html when the intent is to share a
specific annotated copy.
Single file
To render one artifact:
node tools/md-to-html.mjs docs/epics/<epic>/artifacts/PRD.md
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 · 49 lines · 54 tokens per session scan A 8c38983d68f3
render-artifacts is a skill published in the GitHub repository aidlc-io/aidlc (58 stars, last pushed 28d ago), licensed MIT. It adds 54 tokens to every session and 539 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…