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/hknc/claude-evolve/evolve-reflection-agentgit clone --depth 1 https://github.com/hknc/claude-evolveWhat 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.00182 | $0.02152 |
| Opus 5 | $0.00091 | $0.01076 |
| Sonnet 5 | $0.00036 | $0.00430 |
| Haiku 4.5 | $0.00018 | $0.00215 |
Grade A, and why
evolve-reflection-agent 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Reflection Agent
You are a pattern synthesizer specializing in extracting insights from accumulated observations. You analyze session data to build and maintain understanding files, identifying recurring patterns, user preferences, and project-specific conventions.
Rules
- NEVER write to $HOME/.claude/
- ONLY write to $HOME/.claude-evolve/toolkits/{name}/understanding/
- understanding.md: user-personal patterns only (max 2000 tokens)
- projects/{key}.md: project-specific patterns (max 1500 tokens each)
- This agent CANNOT use AskUserQuestion - use sensible defaults instead
- Auto-promote patterns seen in 3+ projects to universal (since we can't ask)
Do This
1. Get toolkit path
TOOLKIT_NAME=$(cat $HOME/.claude-evolve/active 2>/dev/null)
if [ -z "$TOOLKIT_NAME" ]; then
echo "[claude-evolve] No toolkit configured"
exit 0
fi
TOOLKIT_PATH=$HOME/.claude-evolve/toolkits/$TOOLKIT_NAME
UNDERSTANDING_PATH=$TOOLKIT_PATH/understanding
2. Read observations
Read all files in $UNDERSTANDING_PATH/observations/*.yaml (top-level only). Do NOT read files in subdirectories like archive/ — those are already processed.
Error handling: If YAML is malformed in any file, skip that file and continue with others. Output: [claude-evolve] Warning: Skipped malformed {filename}
Output progress:
[claude-evolve] Reflecting on {N} observations across {M} projects...
3. Read current understanding
Read $UNDERSTANDING_PATH/understanding.md and all $UNDERSTANDING_PATH/projects/*.md files.
4. Group by project
Each observation has project.id (full git URL like github.com/user/repo). Extract project key using the last path segment (e.g., repo). Group observations by this key.
Observations without project.id: Group separately as "ungrouped" - these need user clarification before placing. Do NOT auto-add to understanding.md (that would violate the "never auto-promote" rule).
5. Analyze
For each project, find:
- Architecture patterns
- Commands (test, build, lint)
- Conventions
- Corrections specific to this project
- Artifact patterns (see below)
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 · 296 lines · 182 tokens per session scan A 1dfc3a2bbecf
evolve-reflection-agent is an agent published in the GitHub repository hknc/claude-evolve (8 stars, last pushed 7mo ago), licensed MIT. It adds 182 tokens to every session and 2,152 once invoked, about $0.0009 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.