maker-cache

A command for managing MAKER's saved patterns for breaking tasks into smaller steps. A cache is stored data that can be reused later.

In plain words
What is it for?
Use it to list cached decompositions and statistics, inspect a pattern, or clear the pattern cache.
Why use it?
It lets you inspect which patterns are reused and how often they succeed, or clear patterns that should no longer be kept.

Command

Install

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.

agentmods
npx agentmods add commands/forsonny/maker-framework/maker-cache
Clone the repo
git clone --depth 1 https://github.com/forsonny/maker-framework
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 597 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.00597
Opus 5 $0.00008 $0.00298
Sonnet 5 $0.00003 $0.00119
Haiku 4.5 $0.00002 $0.00060

Measured 2d ago against content hash 0084c01322da, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

maker-cache 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.

commands/maker-cache.md · 145 lines

How it starts

The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MAKER Cache Command

Manage the decomposition pattern cache.

Subcommands

Based on $ARGUMENTS:

list

Show all cached decomposition patterns with usage statistics.

==========================================
         MAKER CACHE - LIST
==========================================

Total Patterns: {count}
Cache Directory: cache/decomposition-patterns/

------------------------------------------
PATTERNS BY TYPE
------------------------------------------

CRUD ({count}):
  - crud-api-endpoint (used {N} times, {success_rate}% success)
  - crud-form-component (used {N} times, {success_rate}% success)

ADD_FEATURE ({count}):
  - feature-auth-jwt (used {N} times, {success_rate}% success)

REFACTOR ({count}):
  - refactor-extract-function (used {N} times, {success_rate}% success)

{...other types...}

------------------------------------------
CACHE STATISTICS
------------------------------------------
Total Hits: {count}
Total Misses: {count}
Hit Rate: {percentage}%
Last Updated: {timestamp}

==========================================

clear

Clear the pattern cache (with confirmation).

==========================================
         MAKER CACHE - CLEAR
==========================================

WARNING: This will remove all cached decomposition patterns.

Patterns to remove: {count}
Cache size: {size}

Clearing cache...
Removed {count} patterns.

Cache cleared successfully.

==========================================

inspect

Show details of a specific cached pattern.

==========================================
         MAKER CACHE - INSPECT
==========================================

Pattern ID: {pattern-id}

------------------------------------------
METADATA
------------------------------------------
Created: {timestamp}
Last Used: {timestamp}
Use Count: {count}
Success Rate: {percentage}%
Failure Count: {count}

------------------------------------------
SIGNATURE
------------------------------------------
Task Type: {type}
Complexity: {level}
Keywords: {list}
File Patterns: {list}

------------------------------------------
DECOMPOSITION
------------------------------------------
Total Steps: {N}

[001] {step name}
  Action: {action}

[002] {step name}
  Action: {action}

{...continue for all steps...}

------------------------------------------
EXECUTION HISTORY
------------------------------------------
- {timestamp}: SUCCESS (task-id-001)
- {timestamp}: SUCCESS (task-id-002)
- {timestamp}: FAILED (task-id-003) - {reason}

==========================================

Read the full file on GitHub · 145 lines

Changes

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.

  1. 2d ago First seen · 145 lines · 15 tokens per session scan A 0084c01322da

Subscribe to this mod's changes

maker-cache is a command published in the GitHub repository forsonny/maker-framework (7 stars, last pushed 8mo ago), licensed MIT. It adds 15 tokens to every session and 597 once invoked, about $0.0001 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.