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 skills add claude-world/director-mode-lite --skill evolving-statusgit 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/skills/claude-world/director-mode-lite/evolving-status)<a href="https://agentmods.dev/skills/claude-world/director-mode-lite/evolving-status"><img src="https://agentmods.dev/badge/skills/claude-world/director-mode-lite/evolving-status.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00017 | $0.00458 |
| Opus 5 | $0.00009 | $0.00229 |
| Sonnet 5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
evolving-status 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 8d 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.
What it actually says
Self-Evolving Loop Status
View status, history, and memory metrics for evolving-loop sessions.
Usage
# Current session status
/evolving-status
# Detailed view
/evolving-status --detailed
# View specific report
/evolving-status --report analysis
/evolving-status --report validation
/evolving-status --report decision
/evolving-status --report learning
/evolving-status --report patterns
# View event history
/evolving-status --history
# View skill evolution
/evolving-status --evolution
# View memory system
/evolving-status --memory
# View tool dependencies
/evolving-status --dependencies
Output Example
Status: in_progress
Phase: EXECUTE
Iteration: 3 / 50
Started: 2026-01-14T12:00:00Z
Request: Build REST API with user authentication...
Skill Versions:
executor: v2
validator: v1
fixer: v1
Lifecycle Status:
executor: task-scoped
validator: task-scoped
fixer: task-scoped
Task Type: auth (pattern: auth)
Acceptance Criteria:
[x] AC-F1: GET /users endpoint
[x] AC-F2: POST /users endpoint
[ ] AC-F3: Input validation
Views
| Flag | Description |
|---|---|
--detailed |
Full JSON state |
--report <type> |
View specific report |
--history |
Last 20 events |
--evolution |
Skill version history |
--memory |
Memory system metrics |
--dependencies |
Tool co-usage graph |
Related
- /evolving-loop - Main development loop
- Architecture - Detailed design
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.
- 8d ago First seen · 91 lines · 17 tokens per session scan A 45ad4756316a
evolving-status is a skill published in the GitHub repository claude-world/director-mode-lite (81 stars, last pushed 8d ago), licensed MIT. It adds 17 tokens to every session and 458 once invoked, about $0.0001 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 skills, from other repositories
kanso-handoff
Use when the user wants the current session's context packaged for the next one: "package this session", "carry this context over", "before I /clear", "handoff", "save where we are", "compact this into a prompt for next time". Writes one dense, machine-readable file and prints the resume line. Not for durable repo…
esp32-expert
This skill should be used for ESP32-specific hardware and runtime work in ESP-IDF, Arduino-ESP32, or PlatformIO projects: target/build detection, FreeRTOS tasks and ISRs, memory/DMA, peripherals, power, networking/security, OTA, crash diagnosis, and unattended reliability. Trigger on "debug this ESP32 crash", "review…
session-recap
Document Claude Code sessions by extracting knowledge into cross-referenced documentation. Triggers on "recap the session", "summarize the work", or after significant code changes.
knowledge-bank-lookup
Delegates knowledge bank lookups to Explore subagents with reflections-first strategy that learns from past mistakes. Checks /reflections/ directory before documentation to extract documented failures to avoid and proven approaches to apply. Automatically triggers when user mentions services ([project-a], [project-b]…
kb-ingest
Ingest external sources into the knowledge bank through interactive study or quick filing. Two modes — Quick (summarize → file) and Study (theme-by-theme deep dive with online research and personal notes → multi-layer KB output → optional blog/slack synthesis). Triggers on "ingest this", "study this article", "add to…
session-manager
Manage current Claude Code session metadata — set project, tags, and summary on session.md via Obsidian CLI. Use this skill whenever the user wants to tag, categorize, name, label, summarize, or organize the current session. Triggers on phrases like "tag this session", "this was about X", "mark this as", "session…