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 skills add volodchenkov/claude-sdlc-agents --skill artifact-templatesgit clone --depth 1 https://github.com/volodchenkov/claude-sdlc-agentsWrote 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/volodchenkov/claude-sdlc-agents/artifact-templates)<a href="https://agentmods.dev/skills/volodchenkov/claude-sdlc-agents/artifact-templates"><img src="https://agentmods.dev/badge/skills/volodchenkov/claude-sdlc-agents/artifact-templates/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/volodchenkov/claude-sdlc-agents/artifact-templates"><img src="https://agentmods.dev/badge/skills/volodchenkov/claude-sdlc-agents/artifact-templates.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00073 | $0.09799 |
| Opus 5 | $0.00036 | $0.04900 |
| Sonnet 5 | $0.00015 | $0.01960 |
| Haiku 4.5 | $0.00007 | $0.00980 |
Grade A, and why
artifact-templates scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Verify: `{scoped command — pytest path::name -x / npm test -- --testPathPattern / mypy path / curl ... }` How it starts
The opening of the file, as written. The whole thing — 824 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Artifact Templates
This skill provides the uniform Markdown structure for every artifact produced in the Plane Conductor pipeline.
When you load this skill: find the section matching the artifact you are about to write, copy the template, fill it in. Don't invent structure — uniformity is the whole point.
Storage rules (defined in plane-api.md §2):
| Artifact | Where it lives in Plane |
|---|---|
| REQUIREMENTS | description_html of root issue (the business-analyst) |
| SPEC | description_html of SPEC sub-issue (the system-analyst) |
| ARCH_REVIEW | comment in SPEC sub-issue (the architect) — posted via post_review(sub_uuid=<spawn issue_uuid>, …) |
| SPEC_APPROVED marker | comment in SPEC sub-issue (the architect, after iterations) — posted via mark_spec_approved(spec_sub_uuid=<spawn issue_uuid>, …) |
| Design brief | description_html of Design sub-issue (the designer) |
| PLAN (backend / frontend) | description_html of role sub-issue (the django-developer / the vue-developer / the react-developer) |
| CHANGES (backend / frontend) | comment in role sub-issue (the django-developer / the vue-developer / the react-developer) — posted via post_changes(sub_uuid=<spawn issue_uuid>, target=…, …) |
| Test plan (API / UX) | description_html of test sub-issue (the api-tester / the ui-tester) |
| Bug report | comment in test sub-issue + back-link to relevant Code sub-issue — posted via post_bug_report(test_sub_uuid=<spawn issue_uuid>, affected_sub_uuid=…, …) |
| Test report | comment in test sub-issue (final summary by the api-tester / the ui-tester) |
| Per-artifact REVIEW | comment on the artifact's sub-issue (the reviewer) |
| Cross-cutting REVIEW verdict | comment on root issue (the reviewer) |
All artifacts written as Markdown, then converted to HTML for description_html / comment_html. Plane preserves headings, bold, lists, code blocks, tables, links.
Mandatory footer — Completion Report (every artifact)
Every template below ends with a Completion Report section. Do not omit it — it is what kills the «сделал X, Y, но Z оставил на потом» tail (see agent-base §0b for the full doneness rule).
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.
- 10d ago First seen · 824 lines · 73 tokens per session scan A cf0fa3f3050c
artifact-templates is a skill published in the GitHub repository volodchenkov/claude-sdlc-agents (2 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 9,799 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…