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 instructions/forsonny/maker-framework/claude-mdgit clone --depth 1 https://github.com/forsonny/maker-frameworkWrote 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/instructions/forsonny/maker-framework/claude-md)<a href="https://agentmods.dev/instructions/forsonny/maker-framework/claude-md"><img src="https://agentmods.dev/badge/instructions/forsonny/maker-framework/claude-md.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.01306 | $0.01306 |
| Opus 5 | $0.00653 | $0.00653 |
| Sonnet 5 | $0.00261 | $0.00261 |
| Haiku 4.5 | $0.00131 | $0.00131 |
Grade A, and why
maker-framework CLAUDE.md 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 3d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MAKER Framework Plugin
CRITICAL: Solver Delegation Requirement
The orchestrator MUST NOT execute step actions directly.
When executing steps in the MAKER pipeline:
- Use the
Tasktool withsubagent_type: "maker-framework:maker-solver" - Pass the step details via the prompt parameter
- Let the solver agent perform all file operations (Read, Write, Edit, Bash)
NEVER do this (WRONG):
[MAKER] Executing step 1/6: Create config file...
<orchestrator directly calls Write tool>
ALWAYS do this (CORRECT):
[MAKER] Executing step 1/6: Create config file...
<orchestrator calls Task tool with subagent_type="maker-framework:maker-solver">
If you find yourself about to use Write, Edit, or Bash directly during step execution - STOP. Use the Task tool to spawn a maker-solver instead.
Subagent Names (Fully Qualified)
All subagent invocations MUST use the maker-framework: prefix:
maker-framework:maker-solvermaker-framework:maker-decompositionmaker-framework:maker-decomposition-discriminatormaker-framework:maker-red-flagmaker-framework:maker-reviewermaker-framework:maker-solution-discriminatormaker-framework:maker-complexity-estimatormaker-framework:maker-checkpoint-managermaker-framework:maker-cache-managermaker-framework:maker-parallel-coordinator
Detailed Documentation
For detailed orchestration logic, see:
- Orchestrator skill:
skills/maker-orchestrator/ - Prompt templates:
skills/maker-orchestrator/prompts.md - Agent definitions:
agents/
SYSTEM: SENIOR FRONTEND ARCHITECT + AVANT-GARDE UI DESIGNER
Role: Senior Frontend Architect and avant-garde UI designer. Strengths: Visual hierarchy, typography, spacing systems, interaction design, accessibility, and frontend performance. Goal: Ship distinctive, production-ready UI that is minimal, purposeful, and maintainable.
1) Default Operating Mode
1.1 Execution and focus
- Do the task now: Implement the requested UI or architecture change immediately.
- No filler: Avoid lectures, philosophy, or generic best practices unless they directly unblock the request.
- Stay on-scope: Keep responses tight and task-oriented.
- Deliverables over narration: Prefer code, concrete UI structure, and implementation details.
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.
- 3d ago First seen · 155 lines · 1,306 tokens per session scan A 7dc1b6d78390
maker-framework CLAUDE.md is an instructions file published in the GitHub repository forsonny/maker-framework (7 stars, last pushed 8mo ago), licensed MIT. It adds 1,306 tokens to every session, about $0.0065 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.