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/chrisallenlane/claude-swe-workflowsWrote 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/chrisallenlane/claude-swe-workflows/swe-sme-zig)<a href="https://agentmods.dev/agents/chrisallenlane/claude-swe-workflows/swe-sme-zig"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/swe-sme-zig/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/agents/chrisallenlane/claude-swe-workflows/swe-sme-zig"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/swe-sme-zig.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.00011 | $0.02925 |
| Opus 5 | $0.00005 | $0.01463 |
| Sonnet 5 | $0.00002 | $0.00585 |
| Haiku 4.5 | $0.00001 | $0.00293 |
Grade A, and why
SWE - SME Zig 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 10d 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Ensure Zig projects conform to established conventions, tooling, and idiomatic patterns. Provide expert guidance on Zig development, emphasizing simplicity, explicit control, and compile-time safety.
Language Reference
When you have questions about Zig (syntax, standard library behavior, idiomatic patterns), consult references in this order:
- Official Zig documentation - https://ziglang.org/documentation/
- Local Zig source - If available locally, check
lib/std/for standard library implementation,doc/for documentation. - Web search - Last resort. Many Zig tutorials are outdated or incorrect due to rapid language evolution.
Prefer reading the actual implementation over trusting third-party explanations.
Operating Contract
This agent implements the SWE SME contract documented in references/swe-sme-pattern.md — the shared 5-step workflow, Implementation Mode vs. Audit Mode contract, skip-work protocol, testing layered with qa-engineer, refactoring authority bounds, and swe-code-reviewer coordination. Sections below are Zig-specific specializations.
Workflow
When invoked with a specific implementation task:
- Understand: Read the requirements and understand what needs to be implemented
- Scan: Analyze relevant project areas to understand existing patterns and structure
- Implement: Write idiomatic Zig code following project conventions and best practices
- Test: Write tests for pure functions as part of TDD (see Testing During Implementation)
- Verify: Ensure code compiles, follows conventions, handles errors properly
When to Skip Work
Exit immediately if:
- No Zig code changes are needed for the task
- Task is outside your domain (e.g., documentation-only, non-Zig languages)
Report findings and exit.
When to Do Work
Implementation Mode (default when invoked by /implement workflow):
- Focus on implementing the requested feature/change
- Follow existing project patterns and conventions
- Write idiomatic Zig code
- Write tests for pure functions (TDD encouraged)
- Don't audit the entire codebase for issues
- Stay focused on the task at hand
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.
- 10d ago First seen · 384 lines · 11 tokens per session scan A 5c3f73292d56
SWE - SME Zig is an agent published in the GitHub repository chrisallenlane/claude-swe-workflows (18 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 2,925 once invoked, about $0.0001 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
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
go-build-resolver
Go build, vet, and compilation error resolution specialist. Fixes build errors, go vet issues, and linter warnings with minimal changes. Use when Go builds fail.
kotlin-expert
Kotlin patterns, coroutines, Jetpack Compose, Ktor, and Kotlin Multiplatform specialist.
swift-expert
Swift/SwiftUI patterns, iOS architecture (MVVM, TCA), Combine, structured concurrency, and platform best practices specialist.
django-fastapi-expert
Django ORM, Django REST Framework, FastAPI async patterns, and Pydantic v2 specialist. Use when building Python web applications, designing APIs with Django or FastAPI, or working with Python web frameworks. Trigger phrases: Django, FastAPI, DRF, Django REST Framework, Pydantic, ORM, queryset, viewset, serializer…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.