evaluate

A command that checks whether generated framework files are valid and identifies changes needed before completion.

In plain words
What is it for?
It evaluates a framework README, CLAUDE.md, command files, plugin manifest, settings file, and optional dry-run results.
Why use it?
It provides a review step for catching problems in generated documentation, commands, settings, and plugin metadata.

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/athrael-soju/framework-generator/evaluate
Clone the repo
git clone --depth 1 https://github.com/athrael-soju/framework-generator
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,357 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00008 $0.01357
Opus 5 $0.00004 $0.00678
Sonnet 5 $0.00002 $0.00271
Haiku 4.5 $0.00001 $0.00136

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

Security

Grade B, and why

evaluate scanned grade B with 1 finding 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

**Settings (`output/{date}/{name}/4-generate/{name}/.claude/settings.local.json`):**
commands/evaluate.md · 234 lines

How it starts

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

Evaluate

Validate the generated framework and iterate if needed.

Inputs

Input Source
framework_readme Generate stage output
claude_md Generate stage output
command_files Generate stage output
plugin_manifest Generate stage output
settings_file Generate stage output
dry_run_stage User input

Input Format

Framework README (output/{date}/{name}/4-generate/{name}/README.md):

# {NAME} Framework
{Description}
## Installation
## Commands
## Workflow
{Mermaid diagram}
## Quick Start
## Output Structure
## Principles

CLAUDE.md (output/{date}/{name}/4-generate/{name}/CLAUDE.md):

## Context
## Roles
## Principles
## Stage Execution
## Command Conventions

Command files (output/{date}/{name}/4-generate/{name}/commands/{stage}.md):

---
description: {One line}
argument-hint: "<framework-name>"
---
# {Stage}
## Inputs
### Input Format
## Process
## Output
{Embedded templates}
## Quality Criteria
## Completion

Plugin manifest (output/{date}/{name}/4-generate/{name}/.claude-plugin/plugin.json):

{
  "name": "{framework-name}",
  "version": "1.0.0",
  "description": "{description}",
  "license": "MIT"
}

Settings (output/{date}/{name}/4-generate/{name}/.claude/settings.local.json):

{
  "env": {
    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
  },
  "permissions": {
    "defaultMode": "bypassPermissions"
  }
}

Process

1. Convention Check - Verify structure compliance:

  • README has required sections
  • Command files have valid frontmatter
  • Output templates exist where needed
  • Mermaid diagrams render

2. Completeness Audit - Check for gaps:

  • Every stage in map has a specification
  • Every stage has a command file
  • Quality criteria cover key concerns
  • Feedback loops handle failure modes

3. Consistency Check - Verify alignment:

  • Stage names match across documents
  • Input/output chains connect properly
  • Terminology is consistent

Read the full file on GitHub · 234 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 · 234 lines · 8 tokens per session scan B 2ebe9cd29d26

Subscribe to this mod's changes

evaluate is a command published in the GitHub repository athrael-soju/framework-generator (2 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 1,357 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.