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 ivy00johns/Skill-Madness --skill artifact-publishgit clone --depth 1 https://github.com/ivy00johns/Skill-MadnessWrote 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/ivy00johns/skill-madness/artifact-publish)<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/artifact-publish"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/artifact-publish/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/ivy00johns/skill-madness/artifact-publish"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/artifact-publish.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.00224 | $0.02137 |
| Opus 5 | $0.00112 | $0.01069 |
| Sonnet 5 | $0.00045 | $0.00427 |
| Haiku 4.5 | $0.00022 | $0.00214 |
Grade A, and why
artifact-publish 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 12d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Artifact Publish
Publishing an Artifact renders a self-contained HTML (or Markdown) file to a hosted, default-private web page on claude.ai — one the user can open in a browser and later choose to share by link. It is the Claude Code Artifact feature documented at code.claude.com/docs/en/artifacts, and it turns "here's a file, open it locally" or a wall of terminal text into a real, shareable page.
This skill is about the decision (when to publish) and the mechanics (how to publish correctly) — not visual design.
Load
artifact-designfirst. It calibrates how much design investment a request warrants and carries the look-and-feel fundamentals. This skill deliberately does not reinvent that guidance — it defers to it.artifact-designis the how it looks;artifact-publishis the should-I-publish-and-how-do-I-ship-it.
Announce at start: "Using artifact-publish to ship [thing] as a hosted Artifact."
When to publish — and when not to
Publishing is the right move when the deliverable is visual or interactive and reads better as a page than as terminal text or a file the user has to find and open:
- a dashboard, KPI board, or analytics view
- a rendered report or a formatted document meant to be read, not grepped
- a chart, a diagram, a data visualization
- a side-by-side comparison of options, designs, or approaches
- an interactive prototype or a code-built mockup
- a walkthrough or explainer with live elements
Do not publish when:
- the output is source code the user will edit — attach the file instead
- the output is the canonical copy of something that lives in the repo (e.g.
interactive-doc's.md) — the Artifact is a shared view, never the source of truth - a plain-text answer is enough — just answer inline
- the content contains secrets, credentials, or data the user hasn't okayed for an external service
Publishing is outward-facing. Even a default-private Artifact is hosted on claude.ai and may be cached or indexed. For anything the user might consider private or sensitive, confirm before you publish — the same discipline you'd apply to any action that sends content off the machine.
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.
- 12d ago First seen · 98 lines · 224 tokens per session scan A 911dff77bc73
artifact-publish is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed yesterday), licensed MIT. It adds 224 tokens to every session and 2,137 once invoked, about $0.0011 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.
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…
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…
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…