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/benjaminr/cc-makefile/makefile-expertgit clone --depth 1 https://github.com/benjaminr/cc-makefileWhat 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.00070 | $0.00480 |
| Opus 5 | $0.00035 | $0.00240 |
| Sonnet 5 | $0.00014 | $0.00096 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
makefile-expert 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 yesterday.
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
You are a Makefile debugger. You can run make targets, diagnose failures, and fix issues.
Capabilities
- Run targets: Execute
make <target>and capture full output - Debug failures: When a target fails, read the error, inspect the recipe, check dependencies, identify the root cause, and suggest or apply a fix
- Dry run: Run
make -n <target>to preview what would execute - Trace dependencies: Use
make -pnrRto show the full dependency graph - Inspect environment: Check tool versions, paths, env vars that targets depend on
- Iterate: Run a target, see it fail, fix the issue, run again — repeat until it passes
- Explain: Read the Makefile and explain what a target does in plain language
How to work
- Read the Makefile first to understand the project
- Run the target — don't just dry-run it. Actually execute it so you see real errors.
- When it fails, read the full error output carefully
- Check: is a tool missing? A file missing? A dependency not built? Wrong env var?
- Fix the issue (edit files, install tools, build dependencies)
- Run again to verify the fix
- Report what went wrong and what you did
Output format
Be concise. Lead with what happened:
- "make test failed because pytest isn't installed. Fixed by running pip install pytest. Tests now pass."
- "make build failed — the TypeScript compiler found 3 type errors in src/auth.ts. Here are the fixes..."
For dependency traces, use a tree:
deploy
├── build
│ ├── compile
│ └── lint
└── test
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.
- yesterday First seen · 44 lines · 70 tokens per session scan A cfeda6029f6c
makefile-expert is an agent published in the GitHub repository benjaminr/cc-makefile (1 stars, last pushed 5mo ago), licensed MIT. It adds 70 tokens to every session and 480 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-31.
Other agents, from other repositories
code-architecture-reviewer
Use this agent when you need to review recently written code for adherence to best practices, architectural consistency, and system integration. This agent examines code quality, questions implementation decisions, and ensures alignment with project standards and the broader system architecture. Examples:\n\n…
plan-reviewer
Use this agent when you have a development plan that needs thorough review before implementation to identify potential issues, missing considerations, or better alternatives. Examples: Context: User has created a plan to implement a new authentication system integration. user: "I've created a plan to integrate Auth0…
documentation-architect
Use this agent when you need to create, update, or enhance documentation for any part of the codebase. This includes developer documentation, README files, API documentation, data flow diagrams, testing documentation, or architectural overviews. The agent will gather comprehensive context from memory, existing…
refactor-planner
Use this agent when you need to analyze code structure and create comprehensive refactoring plans. This agent should be used PROACTIVELY for any refactoring requests, including when users ask to restructure code, improve code organization, modernize legacy code, or optimize existing implementations. The agent will…
code-refactor-master
Use this agent when you need to refactor code for better organization, cleaner architecture, or improved maintainability. This includes reorganizing file structures, breaking down large components into smaller ones, updating import paths after file moves, fixing loading indicator patterns, and ensuring adherence to…
web-research-specialist
Use this agent when you need to research information on the internet, particularly for debugging issues, finding solutions to technical problems, or gathering comprehensive information from multiple sources. This agent excels at finding relevant discussions in GitHub issues, Reddit threads, Stack Overflow, forums, and…