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.
git 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/plugins/thevibeworks/claude-code-docs/project-artifact)<a href="https://agentmods.dev/plugins/thevibeworks/claude-code-docs/project-artifact"><img src="https://agentmods.dev/badge/plugins/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/plugins/thevibeworks/claude-code-docs/project-artifact"><img src="https://agentmods.dev/badge/plugins/thevibeworks/claude-code-docs/project-artifact.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
What it actually says
{
"name": "project-artifact",
"description": "Generate and publish a project status artifact — an opinionated, tabbed status page (overview & success criteria, the workstream sequence, next steps, plus background / plan / risks & open questions / decisions-FAQ when they earn a tab) published via the built-in Artifact tool to a default-private claude.ai page the user can share with teammates. Each artifact is backed by a per-project config, so 'refresh the artifact' re-gathers live state, redeploys the same URL, and reports only the delta. Domain-neutral, with a software specialization for projects whose workstreams are pull requests. Needs the built-in Artifact tool (claude.ai login).",
"author": {
"name": "Anthropic",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 202 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 9 lines scan A d695cb344428
project-artifact is a plugin published in the GitHub repository thevibeworks/claude-code-docs (40 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
flow
The /flow engine — one unified, PM-agnostic workflow system spanning capture → done. Manual stages and an autonomous loop seated on DorkOS Pulse.
living-manual
Generate and maintain a branded, interactive user's manual from any codebase: clickable headings file notes that become developer tickets (optionally synced to Jira or GitHub Issues), roadmap previews show planned changes, a glossary explains concepts on first use, and readers reorder sections by dragging the contents.
okf
Create, follow, and continuously maintain an Open Knowledge Format (OKF) knowledge catalog in every project — a vendor-neutral, plain-markdown standard. Bundles the okf-catalog skill, the okf-auditor agent, and a SessionStart hook that flags any project missing a catalog.
bounty-board
Turns your repo's tech debt into an aging bounty economy. A SessionStart hook scans tracked files and prices each TODO/FIXME/HACK/skip as a wanted-poster bounty whose XP grows with its git-blame age, injects the top 3 as opportunistic side quests, and, via a PostToolUse hook, verifies and pays out bounties that…
g-forge
Educated, enforced project management for AI development - a PM layer, parallel implementation waves, and a git-hook commit gate that can't be skipped. Make any model ship like a senior team.
analyze-issue
Fetches GitHub issue details to create comprehensive implementation specifications, analyzing requirements and planning structured approach with clear implementation steps.