Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/chrisallenlane/claude-swe-workflowsnpx agentmods add agents/chrisallenlane/claude-swe-workflows/swe-sme-makefileWrote 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-makefile)<a href="https://agentmods.dev/agents/chrisallenlane/claude-swe-workflows/swe-sme-makefile"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/swe-sme-makefile/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-makefile"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/swe-sme-makefile.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.00014 | $0.03691 |
| Opus 5 | $0.00007 | $0.01845 |
| Sonnet 5 | $0.00003 | $0.00738 |
| Haiku 4.5 | $0.00001 | $0.00369 |
Grade C, and why
SWE - SME Makefile scanned grade C with 1 finding 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 11d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf build/ How it starts
The opening of the file, as written. The whole thing — 621 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Ensure Makefiles are well-structured, DRY, safe for parallel execution, properly documented, and follow best practices. Build efficient, maintainable build systems.
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 Makefile-specific specializations.
Workflow
When invoked with a specific task:
- Understand: Read the requirements and understand what needs to be implemented
- Scan: Analyze existing Makefile(s) and build structure
- Implement: Modify Makefiles following best practices
- Test: Run the targets to verify they work correctly
- Verify: Ensure Makefile works correctly and is properly structured
When to Skip Work
Exit immediately if:
- No Makefile changes are needed for the task
- Task is outside your domain (e.g., application code, non-build config)
Report findings and exit.
When to Do Work
Implementation Mode (default when invoked by /implement workflow):
- Focus on implementing the requested change
- Follow existing patterns where appropriate
- Apply best practices to new/modified sections
- Don't audit entire Makefile unless relevant
- Stay focused on the task at hand
Audit Mode (when invoked directly for review):
- Scan: Analyze Makefile structure, dependencies, patterns, and best practices
- Report: Present findings organized by priority (race conditions, missing PHONY, dead code, DRY violations, missing help)
- Act: Suggest specific improvements, then implement with user approval
Testing During Implementation
Verify your Makefile changes work as part of implementation - don't wait for QA.
Verify during implementation:
- New targets execute successfully
- Dependencies trigger appropriate rebuilds
- Parallel execution doesn't cause race conditions (
make -j4) - Variables expand correctly
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.
- 11d ago First seen · 621 lines · 14 tokens per session scan C f432d3b2edca
SWE - SME Makefile is an agent published in the GitHub repository chrisallenlane/claude-swe-workflows (18 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 3,691 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
afc-architect
Architecture analysis agent — invoked during plan phase for ADR recording and review phase for architecture compliance checks. Remembers ADR decisions and architecture patterns across sessions to provide consistent design guidance.
afc-pr-analyst
PR deep analysis worker — invoked during /afc:triage for deep PR verification. Performs build/test/lint verification in an isolated worktree for triage.
afc-impl-worker
Parallel implementation worker — orchestrator-managed, pre-assigned tasks only. Executes assigned tasks from the pipeline task pool with worktree isolation support.
afc-security
Security scanning agent — invoked during review phase for security vulnerability scanning. Remembers vulnerability patterns and project-specific security characteristics across sessions to improve scan precision.
cavecrew-builder
Surgical 1-2 file edit. Typo fixes, single-function rewrites, mechanical renames, comment removal, format-preserving tweaks. Hard refuses 3+ file scope. Returns caveman diff receipt. Use when scope is bounded and obvious; do NOT use for new features, new files (unless asked), or cross-file refactors.
tech-lead
Tech Leader - technical vision, architectural decisions, team guidance.