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/theclaymethod/artifactureWrote 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/theclaymethod/artifacture/artifacture)<a href="https://agentmods.dev/plugins/theclaymethod/artifacture/artifacture"><img src="https://agentmods.dev/badge/plugins/theclaymethod/artifacture/artifacture/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/theclaymethod/artifacture/artifacture"><img src="https://agentmods.dev/badge/plugins/theclaymethod/artifacture/artifacture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
visual-explainer-marketplace 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 1mo 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
89% identical to visual-explainer-marketplace — 4 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": "visual-explainer-marketplace",
"description": "Artifacture plugins",
"version": "1.0.0"
}
What it installs
The manifest is a name and a version. 1 plugin travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
- 1mo ago Changed c061b09ece98
- 1mo ago First seen · 6 lines scan A ce570074feb3
visual-explainer-marketplace is a plugin published in the GitHub repository theclaymethod/artifacture (3 stars, last pushed 5d ago), 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 89% identical to visual-explainer-marketplace, differing in 4 lines, and is treated as a copy.
Other plugins, from other repositories
han-communication
Foundational communication plugin for the Han suite. Owns the canonical readability standard, the writing-voice profile, and the explanation standard for talking to a reader who will not implement the work, plus the readability-guidance skill that surfaces the first two into a calling skill's own context for in-voice…
handbook-agent-spec-kit
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation.
go-ultimate
Opinionated Go development skill — architecture, conventions, production readiness, repo/CI hygiene, review, and MCP/agent patterns.
deadeye
Fits model, effort, and context to each task via a deterministic policy kernel behind Claude Code hooks. He doesn't waste shots.
looptimal
Turns an objective into a delivered, VERIFIED OUTCOME: frames a hash-pinned sealed acceptance suite, designs the right loop (the loop-design wizard, formerly LoopPrint), war-games it forward, executes with dynamic domain-expert sub-agents (maker != checker), and gates completion on a separate verifier re-running the…
ar
ar — autoresearch: a skill-only autonomous experiment loop. Propose → measure → keep winners → repeat, against any numeric objective, with noise-floor gating so nothing is banked on noise. Five skills: /ar:start opens a run (dedicated branch + baseline noise floor), /ar:resume advances it, /ar:status prints read-only…