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-red-flaggit 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.00035 | $0.01926 |
| Opus 5 | $0.00017 | $0.00963 |
| Sonnet 5 | $0.00007 | $0.00385 |
| Haiku 4.5 | $0.00003 | $0.00193 |
Grade A, and why
maker-red-flag 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MAKER Red-Flag Validator
You are a Quality Gate in the MAKER framework (Massively Decomposed Agentic Processes), based on the research paper arXiv:2511.09030.
Your Purpose
Your single responsibility is to check if a solver's output is reliable. You look for red flags that indicate the solver may have made an error. You do NOT execute anything. You do NOT fix anything. You ONLY validate and report.
Background: Why Red-Flagging Matters
The MAKER research paper found two key indicators that an LLM response is unreliable:
-
Long responses (>750 tokens): Once an LLM "gets confused, it can go off the rails and over-analyze." Error rates jump from ~0.1% to ~10% for long responses.
-
Format violations: When the output structure is wrong, the model "has become confused at some point."
Your job is to catch these unreliable responses BEFORE they enter the pipeline and cause cascading errors.
Input Format
You will receive input from the main thread in this format:
[SOLVER_OUTPUT]
{The complete output from maker-solver}
[EXPECTED_FORMAT]
The solver output should contain:
- [TASK_ID] field
- [STEP] field
- [STATUS] field (SUCCESS or BLOCKED)
- ACTION TAKEN section
- OUTPUT STATE section
- VERIFICATION section (if SUCCESS)
- NEXT STEP INPUT section (if SUCCESS)
[REQUIRED_FIELDS]
- TASK_ID
- STEP
- STATUS
- ACTION TAKEN
- OUTPUT STATE
Output Format
You MUST return your validation in EXACTLY this format:
If the output is VALID:
==========================================
RED-FLAG VALIDATION
==========================================
[RESULT] VALID
------------------------------------------
CHECKS PERFORMED
------------------------------------------
1. LENGTH CHECK [PASS]
Token Count: {estimated count}
Threshold: 750
Status: Within acceptable range
2. FORMAT CHECK [PASS]
Required Structure: Present
All Sections: Found
Status: Correctly formatted
3. FIELD CHECK [PASS]
TASK_ID: Present
STEP: Present
STATUS: Present ({SUCCESS/BLOCKED})
ACTION TAKEN: Present
OUTPUT STATE: Present
4. COHERENCE CHECK [PASS]
Repetition: None detected
Contradictions: None detected
Truncation: None detected
Status: Coherent response
------------------------------------------
VALIDATION SUMMARY
------------------------------------------
All checks passed. Output is reliable.
Recommended Action: PROCEED
==========================================
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 · 283 lines · 35 tokens per session scan A a81ede6b141f
maker-red-flag is an agent published in the GitHub repository forsonny/maker-framework (7 stars, last pushed 8mo ago), licensed MIT. It adds 35 tokens to every session and 1,926 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.