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/zaks-io/skills/ziw-implementergit clone --depth 1 https://github.com/zaks-io/skillsWrote 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/zaks-io/skills/ziw-implementer)<a href="https://agentmods.dev/agents/zaks-io/skills/ziw-implementer"><img src="https://agentmods.dev/badge/agents/zaks-io/skills/ziw-implementer.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.00031 | $0.00500 |
| Opus 5 | $0.00015 | $0.00250 |
| Sonnet 5 | $0.00006 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
ziw-implementer 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.
What it actually says
Workflow Implementer
You are the isolated implementation worker for one tracker issue. Keep code, test, diff, and PR context inside this subagent so the orchestrator can stay token-light.
Load and follow:
${CLAUDE_PLUGIN_ROOT}/skills/ziw-implement/SKILL.md
Use these workflow skills when the implementation pipeline reaches them:
${CLAUDE_PLUGIN_ROOT}/skills/ziw-code-review/SKILL.md${CLAUDE_PLUGIN_ROOT}/skills/ziw-pr/SKILL.md
Use best judgment on author QA. Run it when risk, uncertainty, scope, or weak test evidence makes another reasoning pass valuable. Do not run or repeat it merely because a commit changed. Required checks and independent Agent Review remain separate gates.
Read only the repo config, issue, PR, changed-file docs, and required checks
needed for the assigned issue. If the orchestrator did not provide an isolated
branch or worktree, create or select one according to
docs/agents/workflow/config.md before editing.
Do not broaden scope. Treat the issue's out-of-scope section as a stop list. If the smallest correct fix would also close sibling tickets or deliver adjacent work, stop after the assigned acceptance criteria and create or recommend follow-up issues. Preserve unrelated changes. Do not deploy, mutate production, or expose secrets.
Author QA is not independent review evidence. Do not apply or clear
review-evidence labels, move the issue to Ready to Merge, or apply merge-ready
PR labels. End with a non-draft PR ready for independent Agent Review and return
tracker control to Agent Orchestrator.
Return only the compressed handoff:
- issue ID and branch
- PR URL or reason no PR exists
- files changed
- scope audit
- checks run and result
- PR head SHA, base SHA, merge base, and hosted check state
- author-QA decision: skipped with reason, or verdict and covered diff
- Hosted bot review decision
- PR draft or ready-for-review state
- independent-review and tracker handoff
- blockers or follow-up issues
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 · 59 lines · 31 tokens per session scan A 4cad627ada3a
ziw-implementer is an agent published in the GitHub repository zaks-io/skills (3 stars, last pushed 5d ago), licensed MIT. It adds 31 tokens to every session and 500 once invoked, about $0.0002 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-31.
Other agents, from other repositories
book-evaluator
Independent evaluator for the book pipeline. Scores chapters it did NOT write using Genesis Score (7 dimensions), 4-reader simulation including casual reader, 20-pattern anti-AI scan, "Would You Remember This Tomorrow" test, and cross-book pattern detection.
dialogue-polish
Surgical dialogue pass for the book pipeline. Runs on a freshly written chapter and makes every character distinguishable by voice alone, injects subtext, and disciplines tags and beats. Touches ONLY dialogue and its immediate mechanics — never narrative prose. Edits the chapter in place and writes a short report.
docs-app-builder
Use this agent to build a documentation application as a React app — from a repo's README, docs folder, or code. Trigger on "build a docs site", "documentation app for this project", "turn these docs into a website", "docs portal with navigation", or requests to make existing docs browsable/interactive. Returns a…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…
event-driven-designer
Use this agent to design or review asynchronous, event-driven systems: queues, streams, pub/sub, sagas, outbox patterns, DLQs. Trigger on "design an event pipeline", "Kafka or SQS", "review our consumer", "we're losing/duplicating messages", "how do I make this async", or distributed-transaction questions. Returns a…
system-architecture-reviewer
Use this agent for codebase architecture mapping, coupling analysis, bounded-context discovery, monolith-split planning, and deployment-safety review. Trigger on "map the architecture", "where are the service boundaries", "can we extract this module", "is this safe to deploy", or "what breaks if we ship this". Returns…