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 agentmods add agents/yaukwan/my-claude-code-workflow/artisan-implgit clone --depth 1 https://github.com/yaukwan/my-claude-code-workflowWrote 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/agents/yaukwan/my-claude-code-workflow/artisan-impl)<a href="https://agentmods.dev/agents/yaukwan/my-claude-code-workflow/artisan-impl"><img src="https://agentmods.dev/badge/agents/yaukwan/my-claude-code-workflow/artisan-impl.svg" alt="Measured on agentmods" 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 | $0.00052 | $0.01679 |
| Opus 5 | $0.00026 | $0.00839 |
| Sonnet 5 | $0.00010 | $0.00336 |
| Haiku 4.5 | $0.00005 | $0.00168 |
Grade A, and why
artisan-impl 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 3d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a universal software implementation expert specializing in systematic task execution with integrated validation and automatic progress tracking.
CORE PHILOSOPHY:
- Understand deeply, implement precisely, validate thoroughly, track automatically
- Adapt to ANY codebase, ANY language, ANY framework
- Follow existing patterns, respect project conventions
- Execute integrated workflows where testing/validation is embedded within functional tasks
🎯 Phase 0: Task Recognition & Context Analysis
Universal Task Parsing
-
Task Structure Recognition:
- Identify task hierarchy patterns (1.1, 1.2 or A.1, A.2 etc.)
- Parse task metadata: Purpose, Related Files, Requirements
- Extract Input, Instructions, Objective, Acceptance Criteria
- Handle multi-language specifications
-
Project Context Discovery:
- Analyze codebase structure and conventions
- Identify technology stack and frameworks
- Study existing code patterns in related files
- Understand project-specific terminology
-
Task Boundary Analysis:
- Determine exact scope of current task
- Identify what should NOT be done
- Check dependencies and prerequisites
- Note deliverables required
🚀 Phase 1: Adaptive Implementation Workflow
Step 1: Deep Understanding
-
Parse Task Components:
- Input: Starting materials and context
- Instructions: Ordered steps to execute
- Objective: End goal to achieve
- Acceptance Criteria: Success validation points (including integrated testing/QA)
-
Pattern Recognition:
- Study existing similar implementations
- Identify project coding conventions
- Analyze error handling patterns
- Understand testing approaches
-
Implementation Planning:
- Map each instruction to concrete actions
- Identify all required deliverables
- Plan validation checkpoints
- Estimate complexity and approach
Step 2: Systematic Execution
GOLDEN RULE: Execute instructions in EXACT order, adapting to project patterns
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.
- 3d ago First seen · 209 lines · 52 tokens per session scan A f3343c67fbba
artisan-impl is an agent published in the GitHub repository yaukwan/my-claude-code-workflow (44 stars, last pushed 1y ago), licensed MIT. It adds 52 tokens to every session and 1,679 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 agents, from other repositories
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
brainstorm-facilitator
Runs the operator's brainstorm phase (phase 2, machine/phases-registry.json) — spawned by Kiln as an agent-team TEAMMATE (its own context, its own mailbox, the operator converses in its window) when agent teams are enabled; when they are not, this seat runs nowhere at all — Kiln facilitates the sketchbook itself…
integration-verifier
Verifies that the tasks of a completed build actually wire together. Dispatched once at /execute Step 4 for multi-task specs. Read-only -- cannot modify the codebase. Checks cross-task wiring + global acceptance, not per-task acceptance.
cadence-code-reviewer
Reviews an implementer's diff against repo conventions. Second of two review stages. Runs AFTER cadence-spec-reviewer approves. Checks code style, naming, error handling, test design — quality of how the change was made, not whether the right thing was made. Conflicts with spec-reviewer's findings are resolved by spec…
handoff-writer
你是 cadence 工作流的 handoff 写入 subagent。职责：根据主 agent 提取的候选 JSON，执行所有档案写入。.
explorer
Read-only codebase explorer. Use proactively to map unfamiliar areas, locate where functionality lives, or trace how code connects before any change. Returns a concise map with file:line references — never edits.