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 thevibeworks/claude-code-docs --skill project-artifactgit clone --depth 1 https://github.com/thevibeworks/claude-code-docsWrote 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/thevibeworks/claude-code-docs/project-artifact)<a href="https://agentmods.dev/skills/thevibeworks/claude-code-docs/project-artifact"><img src="https://agentmods.dev/badge/skills/thevibeworks/claude-code-docs/project-artifact/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/thevibeworks/claude-code-docs/project-artifact"><img src="https://agentmods.dev/badge/skills/thevibeworks/claude-code-docs/project-artifact.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.00202 | $0.04900 |
| Opus 5 | $0.00101 | $0.02450 |
| Sonnet 5 | $0.00040 | $0.00980 |
| Haiku 4.5 | $0.00020 | $0.00490 |
Grade A, and why
project-artifact 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 5d 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.
This is a copy
100% identical to project-artifact — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
project-artifact — an opinionated project status page
This skill produces one specific kind of artifact: a tabbed status page that represents a
project too big for one update — a software migration, a research effort, a launch, an org
initiative; anything with a set of parallel/dependent workstreams tracked over time. It
generates the HTML (one file, self-contained — the Artifact CSP blocks all external hosts,
so everything is inlined; the only <script> is the tab switcher) and publishes it with
the built-in Artifact tool to https://claude.ai/code/artifact/<uuid>. The page is
default-private; the viewer gives the owner a version picker and lets them share it with
teammates. (The general "render any HTML/Markdown to a web page" capability is the built-in
Artifact tool; this is the project-tracker structure on top — defining what an artifact
is belongs to that tool, not here.)
The SWE specifics for PR-driven projects are in swe.md, kept out of this file so the
project-artifact structure stays domain-neutral.
Workflow
- Resolve the artifact config, then locate the project. Each project gets a directory
at
${CLAUDE_PLUGIN_DATA}/artifacts/<slug>/holdingconfig.md(see "The artifact config" below) andpage.html(the current render); listingartifacts/is the registry of this skill's artifacts on this machine (enumerate it with Glob or a directory read — a shell listing of the data dir can be blocked in restricted environments). If the user names a project, load that slug; if exactly one config matches the session (its repo is the cwd, or its project came up in conversation), use it; a config that exists means this is a refresh — follow "Refreshing an artifact" below. No config means a first build: gather from scratch and write the config after the first publish — but if the user says the project already has a published artifact (made on another machine or in a lost session), get that URL and record it instead of minting a new one. Then collect the source material: the goal, the set of workstreams (PRs, milestones, sub-projects, tasks), owners, dates, and any sibling docs (design doc, plan, spec). Pull whatever the domain gives you cheaply — always live, never from memory or earlier turns — for software that'sgh pr list/git log/gh pr view(seeswe.md); for other domains it's the project doc, a tracker, a spreadsheet, your own notes. If the source is itself an existingclaude.ai/code/artifact/...page to reshape, fetch it — see "Reading an existing artifact page" below. Don't ask the user to paste content or hand you a local file as a substitute for fetching it yourself.
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.
- 5d ago First seen · 262 lines · 202 tokens per session scan A 34e13249dba8
project-artifact is a skill published in the GitHub repository thevibeworks/claude-code-docs (40 stars, last pushed yesterday), licensed MIT. It adds 202 tokens to every session and 4,900 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to project-artifact, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
sync
Synchronize task files and source-of-truth documents. Update NEXT-TASKS.md, FUTURE-ENHANCEMENTS.md, README, and CHANGELOG to reflect current project state.
auditing-ui
Runs a lens-based UI/UX audit of the client and turns its findings into tracked, fenced work items. Use when auditing the interface for quality gaps, running or scoping an audit (full, one lens, one surface, or a diff), driving the real-browser leg of an audit, synthesizing raw lens findings into batches, or deciding…
orchestrating-parallel-work
Orchestrates parallel execution of AI agents with dependency analysis, batch scheduling, and the playbook for landing many branches at once. Use when coordinating multiple concurrent tasks, optimizing task ordering, sequencing batches of code changes into waves, landing parallel branches through review and merge, or…
managing-specs
Canonical rules for spec manifest management — statuses, transitions, and the manifest-ops script. Auto-loads when working with spec files.
dorkbot-triage
First-touch triage for incoming GitHub issues on dork-labs/dorkos. Use when DorkBot is asked to triage the issue queue: label each new issue by type and runtime, find likely duplicates, and ask the reporter for missing reproduction steps. Read-and-suggest by default; only comments or edits labels when explicitly…
okf-catalog
Create, follow, and continuously update an Open Knowledge Format (OKF) knowledge catalog for a project. Use whenever starting a project, documenting project knowledge (tables, datasets, metrics, APIs, playbooks, decisions, runbooks), or when an OKF bundle needs a new/updated concept doc, index.md, or log.md entry.…