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.
git clone --depth 1 https://github.com/athrael-soju/framework-generatorWrote 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/commands/athrael-soju/framework-generator/evaluate)<a href="https://agentmods.dev/commands/athrael-soju/framework-generator/evaluate"><img src="https://agentmods.dev/badge/commands/athrael-soju/framework-generator/evaluate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/athrael-soju/framework-generator/evaluate"><img src="https://agentmods.dev/badge/commands/athrael-soju/framework-generator/evaluate.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00008 | $0.01357 |
| Opus 5.5 | $0.00003 | $0.00543 |
| Sonnet 5.5 | $0.00002 | $0.00271 |
| Haiku 4.5 | $0.00001 | $0.00136 |
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 1mo 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`):** 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
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.
- 1mo ago First seen · 234 lines · 8 tokens per session scan B 2ebe9cd29d26
evaluate is a command published in the GitHub repository athrael-soju/framework-generator (2 stars, last pushed 8mo ago), licensed MIT. It adds 8 tokens to every session and 1,357 once invoked, about $0.0000 per session on Opus 5.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.
Other commands, from other repositories
review-pr
Review a pull request or the current branch with four specialist agents in parallel (code-reviewer for correctness and security, silent-failure-hunter, test-gap-analyzer, type-design-reviewer), then merge their findings into one severity-ranked review with file:line anchors and no duplicates, optionally posted to the…
write-tests
Generate a focused, production-quality test suite for a source file, detecting the project's existing test runner and conventions. Use when a source file needs a test suite that matches the project's existing conventions.
feature
Take a feature from a one-line description to a reviewed, tested change through a fixed pipeline: orient with the code-explorer agent, clarify requirements, write a task-by-task plan with the writing-plans skill, execute it with test-driven development, simplify with the code-simplifier agent, verify completion, and…
validate
Mechanically validate the sonu plugin repo before a PR — manifest sync, YAML frontmatter, shell-fence syntax, named-source and AI-attribution scans, cross-reference integrity, skill reachability. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
check
Quick health check (git, lint, unit tests).
test
Run tests related to the modified files.