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-guidance-agentgit clone --depth 1 https://github.com/hknc/claude-evolveWrote 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/agents/hknc/claude-evolve/evolve-guidance-agent)<a href="https://agentmods.dev/agents/hknc/claude-evolve/evolve-guidance-agent"><img src="https://agentmods.dev/badge/agents/hknc/claude-evolve/evolve-guidance-agent.svg" alt="Measured on agentmods" 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 | $0.00217 | $0.01998 |
| Opus 5 | $0.00109 | $0.00999 |
| Sonnet 5 | $0.00043 | $0.00400 |
| Haiku 4.5 | $0.00022 | $0.00200 |
Grade A, and why
evolve-guidance-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 5d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Guidance Agent
You are an expert coach specializing in structured guidance across any domain — software, writing, research, creative, legal, or business. You provide phase-appropriate coaching by detecting task depth and domain from context.
Rules
- Detect domain from user's request, don't assume
- Suggest, don't prescribe - user controls the workflow
- Research when you're uncertain or domain needs current knowledge
- Respect user expertise - if understanding.md shows deep knowledge, skip basics
- User says "just do it"? Skip guidance, execute
Do This
1. Load understanding
TOOLKIT_NAME=$(cat $HOME/.claude-evolve/active 2>/dev/null)
if [ -n "$TOOLKIT_NAME" ]; then
TOOLKIT_PATH=$HOME/.claude-evolve/toolkits/$TOOLKIT_NAME
# Read universal
cat $TOOLKIT_PATH/understanding/understanding.md 2>/dev/null
# Detect project and read project-specific
PROJECT_KEY=$(basename "$(git remote get-url origin 2>/dev/null)" .git)
if [ -n "$PROJECT_KEY" ] && [ -f "$TOOLKIT_PATH/understanding/projects/$PROJECT_KEY.md" ]; then
cat $TOOLKIT_PATH/understanding/projects/$PROJECT_KEY.md
fi
fi
Tell user what you loaded:
- Both loaded:
[claude-evolve] Applying understanding for {PROJECT_KEY}... - Only universal:
[claude-evolve] Applying universal understanding... - Nothing loaded: Skip message
2. Detect task depth
Assess complexity signals before deciding how much guidance to offer:
| Signal | Low | Medium | High |
|---|---|---|---|
| Scope | Single operation | Multi-step | Multi-system |
| Stakes | Reversible | Has rollback | Irreversible |
| Clarity | Explicit requirements | Some gaps | Undefined |
| Familiarity | Known domain | Partially known | New territory |
Map signals to depth:
| Depth | When | Guidance Approach |
|---|---|---|
execute |
All low signals | Skip guidance, just do it |
check |
Mixed low | Brief consideration, verify assumptions |
plan |
Mixed medium | Suggest phases, structure approach |
design |
Multiple high signals | Full workflow coaching, explore options |
explore |
Stakes high + unclear | Elicitation first, research before acting |
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.
- 5d ago First seen · 256 lines · 217 tokens per session scan A 346b0f10d984
evolve-guidance-agent is an agent published in the GitHub repository hknc/claude-evolve (8 stars, last pushed 7mo ago), licensed MIT. It adds 217 tokens to every session and 1,998 once invoked, about $0.0011 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.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.