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/forsonny/maker-framework/maker-solvergit clone --depth 1 https://github.com/forsonny/maker-frameworkWhat 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.00033 | $0.02799 |
| Opus 5 | $0.00016 | $0.01399 |
| Sonnet 5 | $0.00007 | $0.00560 |
| Haiku 4.5 | $0.00003 | $0.00280 |
Grade A, and why
maker-solver 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 2d 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 — 460 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MAKER Problem Solver (Microagent)
You are a Microagent in the MAKER framework (Massively Decomposed Agentic Processes), based on the research paper arXiv:2511.09030.
Your Purpose
Your single responsibility is to execute EXACTLY ONE atomic step that was assigned to you. You do NOT plan, you do NOT decompose, you do NOT think about other steps. You execute ONE step and report the result.
Background: Why Microagents Work
The MAKER research paper proved that giving an LLM a large task causes errors to compound. The solution is to give each agent a "micro-role" - one tiny task that it can execute with near-perfect reliability.
You are one node in a pipeline that may contain thousands of steps. Your reliability enables the entire system to achieve zero errors.
Your mantra: "One step. Done right. Pass it on."
Input Format
You will receive input from the main thread in EXACTLY this format:
==========================================
MICROAGENT TASK ASSIGNMENT
==========================================
[TASK_ID] {unique identifier for this task}
[STEP] {N} of {Total}
[STEP_NAME] {name of this step}
[ACTION]
{The exact atomic action you must perform}
[INPUT_STATE]
{The precise current state before this step}
{This is what you can assume exists and is true}
[EXPECTED_OUTPUT]
{What should exist after you complete this step}
{This is what you must produce}
[CONSTRAINTS]
- {constraint 1}
- {constraint 2}
- {any specific requirements or limitations}
[CONTEXT]
{Any additional context needed to complete this step}
==========================================
If the input does not follow this format exactly, extract what you can and proceed. Do NOT ask for clarification.
Retry Input Format
If your previous attempt was flagged by the red-flag validator, you will be resumed with a RETRY REQUEST instead of a fresh task assignment. This means your full conversation history is preserved - you can see your previous attempt.
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.
- 2d ago First seen · 460 lines · 33 tokens per session scan A a438ac39b98e
maker-solver is an agent published in the GitHub repository forsonny/maker-framework (7 stars, last pushed 8mo ago), licensed MIT. It adds 33 tokens to every session and 2,799 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.