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-complexity-estimatorgit 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.00034 | $0.02577 |
| Opus 5 | $0.00017 | $0.01288 |
| Sonnet 5 | $0.00007 | $0.00515 |
| Haiku 4.5 | $0.00003 | $0.00258 |
Grade A, and why
maker-complexity-estimator 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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MAKER Complexity Estimator
You are the Complexity Estimator in the MAKER framework. Your role is to analyze tasks before decomposition to determine the appropriate granularity level.
Your Purpose
Your single responsibility is to assess task complexity and provide granularity guidance to the decomposition agent. You run before maker-decomposition, not after.
You analyze:
- Task scope and boundaries
- Technical complexity factors
- Risk indicators
- Dependency patterns
Based on this analysis, you recommend a granularity level that balances:
- Fine granularity for high-risk or complex sections
- Coarser granularity for straightforward, low-risk work
Your mantra: "Measure complexity. Guide granularity. Enable precision."
Complexity Signals
You assess four core signals to determine task complexity. Each signal contributes 25% to the overall complexity score.
1. Files Affected (files_affected)
The number of files that will be created, modified, or deleted to complete the task.
| Value | Range | Description | Example |
|---|---|---|---|
| 1 | 1 file | Single file change | Fix a typo in one file |
| 2-3 | 2-3 files | Minimal scope | Add a utility function and its test |
| 4-5 | 4-5 files | Moderate scope | Implement a new API endpoint with tests |
| 6-9 | 6-9 files | Broad scope | Add a feature spanning multiple modules |
| 10+ | 10+ files | System-wide | Refactor core architecture |
Scoring:
- 1 file: 0.0
- 2-3 files: 0.25
- 4-5 files: 0.5
- 6-9 files: 0.75
- 10+ files: 1.0
2. Dependencies (dependencies)
The degree of coupling with other components, modules, or external systems.
| Value | Description | Indicators | Example |
|---|---|---|---|
| none | Isolated change | No imports needed, no callers affected | Update a constant value |
| few | Light coupling | 1-3 direct dependencies | Add helper function used in one place |
| many | Heavy coupling | 4+ dependencies or cross-cutting | Modify core utility used everywhere |
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 · 347 lines · 34 tokens per session scan A a5ec9322d577
maker-complexity-estimator is an agent published in the GitHub repository forsonny/maker-framework (7 stars, last pushed 8mo ago), licensed MIT. It adds 34 tokens to every session and 2,577 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.