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 hackersandwizards/artificer --skill build-workflowgit clone --depth 1 https://github.com/hackersandwizards/artificerWrote 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/hackersandwizards/artificer/build-workflow)<a href="https://agentmods.dev/skills/hackersandwizards/artificer/build-workflow"><img src="https://agentmods.dev/badge/skills/hackersandwizards/artificer/build-workflow/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/hackersandwizards/artificer/build-workflow"><img src="https://agentmods.dev/badge/skills/hackersandwizards/artificer/build-workflow.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.00055 | $0.00260 |
| Opus 5 | $0.00028 | $0.00130 |
| Sonnet 5 | $0.00011 | $0.00052 |
| Haiku 4.5 | $0.00006 | $0.00026 |
Grade A, and why
build-workflow 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 9d 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.
What it actually says
Scaffold one workflow stage by orchestrating two subagents with the Task tool, in order:
- New workflow only. If this is the first stage of a new workflow, first spawn the
claude-code-guidesubagent to confirm the current Claude Code docs the scaffolding depends on: subagentStop/SubagentStopgates, whetheragentTypefires those gates inside a workflow, and the dynamic-workflow script API. Skip this on later stages of the same workflow. - Scaffold. Spawn the
build-workflowgenerator agent (subagent typebuild-workflow:build-workflow) and give it the stage spec below plus any doc corrections from step 1. Return its result.
Stage spec:
$ARGUMENTS
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.
- 9d ago First seen · 18 lines · 55 tokens per session scan A 63d075dfb294
build-workflow is a skill published in the GitHub repository hackersandwizards/artificer (16 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 260 once invoked, about $0.0003 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
patpat-loop
Run the explicit Patpat evidence-driven engineering loop. Use only when the user invokes /patpat, /patpat-loop, $patpat, or $patpat-loop, or directly asks to activate Patpat mode.
patpat-architect
Design a repository-native change before implementation. Use for architecture, migrations, public contracts, security-sensitive boundaries, cross-cutting work, or decisions with meaningful compatibility risk.
patpat-run
Drive, checkpoint, validate, resume, or safely take over multi-phase engineering work through a deterministic local state machine. Use for long work, arbitrary branch or handoff pickup, and tasks that must survive context loss without granting delivery authority.
patpat-setup
Inspect the active agent host and install or validate Patpat through its supported native plugin manager or an explicit Agent Skills directory. Use for Patpat installation, discovery, update, removal, or host compatibility questions.
patpat-verify
Prove an implementation or repository claim against its authoritative artifact or user surface. Use after code changes, during acceptance checks, or whenever tests and builds are insufficient evidence of real behavior.
patpat-change
Implement one bounded repository change with a small diff and explicit proof. Use for clear features, localized refactors, and requested fixes after the root cause or design is known.