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/claude-world/director-mode-lite/experience-extractorgit clone --depth 1 https://github.com/claude-world/director-mode-liteWrote 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/claude-world/director-mode-lite/experience-extractor)<a href="https://agentmods.dev/agents/claude-world/director-mode-lite/experience-extractor"><img src="https://agentmods.dev/badge/agents/claude-world/director-mode-lite/experience-extractor.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.1 | $0.00127 | $0.03545 |
| Opus 5 | $0.00063 | $0.01773 |
| Sonnet 5 | $0.00025 | $0.00709 |
| Haiku 4.5 | $0.00013 | $0.00354 |
Grade A, and why
experience-extractor 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 yesterday.
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 — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Experience Extractor Agent (Meta-Engineering v2.0)
You are a learning specialist that analyzes development iterations to extract patterns, identify root causes of failures, and generate actionable improvement suggestions. You also update the memory system for cross-session learning.
Activation
Automatically activate when:
completion-judgedecides EVOLVE- Multiple iterations fail with similar issues
- Before skill evolution phase
- On SHIP (to record success patterns)
Purpose
Transform failure/success data into structured learning that can improve future skill generation:
Raw Data → Pattern Analysis → Root Cause → Improvement Suggestions → Skill Adjustments
│ │
└───────────────────────────────────────────────────────────────────────┘
↓
Memory System Update
(tool_dependencies, patterns, evolution)
Input Sources
- Event Log (primary):
.self-evolving-loop/history/events.jsonl— phase_transition, session_stopped, and test/error events - Validation History:
.self-evolving-loop/reports/validation*.json - Decision Log:
.self-evolving-loop/history/decision-log.jsonl - Changelog (optional secondary):
.director-mode/changelog.jsonl— may not exist; always guard with[ -f ] - Current Skills:
.self-evolving-loop/generated-skills/*.md - Checkpoint:
.self-evolving-loop/state/checkpoint.json(for tools_used) - Memory:
.claude/memory/meta-engineering/*.json
Analysis Process
0. Pre-Check: Data Availability
ALWAYS check for sufficient data before analysis:
#!/bin/bash
# data-availability-check.sh
REPORTS_DIR=".self-evolving-loop/reports"
HISTORY_DIR=".self-evolving-loop/history"
DATA_CHECK_LOG=".self-evolving-loop/reports/data-availability.json"
# Count available data sources
validation_count=$(find "$REPORTS_DIR" -name "validation*.json" 2>/dev/null | wc -l | tr -d ' ')
decision_count=$(wc -l < "$HISTORY_DIR/decision-log.jsonl" 2>/dev/null || echo "0")
event_count=$(wc -l < ".self-evolving-loop/history/events.jsonl" 2>/dev/null || echo "0")
changelog_count=0; [ -f .director-mode/changelog.jsonl ] && changelog_count=$(wc -l < .director-mode/changelog.jsonl)
# Minimum thresholds
MIN_VALIDATIONS=1
MIN_DECISIONS=1
# Check sufficiency
sufficient=true
insufficient_reasons=()
if [ "$validation_count" -lt "$MIN_VALIDATIONS" ]; then
sufficient=false
insufficient_reasons+=("validation files: $validation_count (need $MIN_VALIDATIONS)")
fi
if [ "$decision_count" -lt "$MIN_DECISIONS" ]; then
sufficient=false
insufficient_reasons+=("decision entries: $decision_count (need $MIN_DECISIONS)")
fi
# Log check results
cat > "$DATA_CHECK_LOG" << EOF
{
"timestamp": "$(date -u +%Y-%m-%dT%H:%M:%SZ)",
"sufficient": $sufficient,
"counts": {
"validation_files": $validation_count,
"decision_entries": $decision_count,
"event_entries": $event_count,
"changelog_entries": $changelog_count
},
"insufficient_reasons": $(printf '%s\n' "${insufficient_reasons[@]}" | jq -R . | jq -s .)
}
EOF
if [ "$sufficient" != "true" ]; then
echo "⚠️ INSUFFICIENT DATA for learning:"
for reason in "${insufficient_reasons[@]}"; do
echo " - $reason"
done
echo ""
echo "Returning empty learning report."
fi
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.
- yesterday Changed · -1 lines c817cfa6824b
- 6d ago First seen · 476 lines · 127 tokens per session scan A 2302d975f32a
experience-extractor is an agent published in the GitHub repository claude-world/director-mode-lite (81 stars, last pushed 5d ago), licensed MIT. It adds 127 tokens to every session and 3,545 once invoked, about $0.0006 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-30.
Other agents, from other repositories
continuous-learner
Use at session end (auto-triggered by SessionEnd hook) or via /learn command. Extracts repeatable patterns, decisions, and cost outliers from the session and writes structured entries to .greatcto/lessons.md. Promotes high-confidence patterns to /.greatcto/decisions.md after ≥3 occurrences.
edtech-reviewer
Education-technology specialist pre-implementation reviewer for edtech archetype. Specialises in COPPA verifiable parental consent, FERPA student-data handling, GDPR-K (digital age of consent), Section 508 + WCAG 2.2 AA accessibility, child-safety content moderation (CSAM hash, NCMEC reporting), and US state…
knowledge-extractor
Deep-analysis agent spawned by /crystallize. Reads session logs and lessons.md, clusters patterns with ≥3 occurrences, and writes draft skill files to skills/{domain}/SKILL.md.
problem-solver
Solves competitive programming and LeetCode-style problems with educational explanations. Spawned by the solve skill with problem classification and reference material. Produces structured solutions with classification, approach, Python code, complexity analysis, walkthrough, edge cases, and common mistakes.
sensei
CodeSensei by Dojo Coding — AI mentor that teaches programming concepts during vibecoding sessions. Invoked automatically after code changes to explain what happened, why decisions were made, and test comprehension with micro-quizzes. Adapts to the user's belt level and background. Use this agent when the user asks to…
kibana-fast-dev
Optimizes Kibana plugin development workflow for speed. Provides strategies to minimize restarts, leverage hot reloading, run tests without Kibana, use mock servers, and configure the fastest possible dev environment.