Borrowing it
Nothing to install: this file belongs to aget-framework/aget. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aget-framework/aget/main/.claude/skills/aget-check-evolution/SKILL.mdgit clone --depth 1 https://github.com/aget-framework/agetWrote 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/aget-framework/aget/aget-check-evolution)<a href="https://agentmods.dev/skills/aget-framework/aget/aget-check-evolution"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-check-evolution/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/skills/aget-framework/aget/aget-check-evolution"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-check-evolution.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.01548 |
| Opus 5.5 | $0.00014 | $0.00619 |
| Sonnet 5.5 | $0.00007 | $0.00310 |
| Haiku 4.5 | $0.00003 | $0.00155 |
Grade A, and why
aget-check-evolution 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 15d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- aget-check-evolution — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aget-check-evolution
Monitor the health of the .aget/evolution/ directory by checking file counts, types, naming conventions, and disk usage.
Purpose
Provide self-diagnostic capability for AGET agents to assess their evolution directory health without supervisor intervention.
Execution
When invoked, perform these checks. First verify .aget/evolution/ is a readable directory and the required tools (find, wc, du, jq, Python 3) are available. If a tool or inventory operation fails, report UNAVAILABLE with the failed check; do not turn incomplete readings into an OK result. These checks inspect filenames and JSON syntax, not lesson schema conformance or index-to-file references.
Run each shell block in Bash and inspect its exit status. A nonzero inventory/naming/disk exit means that reading is unavailable, regardless of partial stdout; discard its counts.
1. File Inventory
set -euo pipefail
# Count total files
find .aget/evolution -type f | wc -l
# Count by extension
find .aget/evolution -type f -name "*.md" | wc -l
find .aget/evolution -type f -name "*.json" | wc -l
find .aget/evolution -type f ! -name "*.md" ! -name "*.json" | wc -l
2. Naming Convention Check
Expected L-doc prefix and number width: L###_*.md or L####_*.md (three or four digits, as specified by AGET_LDOC_SPEC.md, CAP-LDOC-001). Examples: L588_skill_invocation_control_semantics.md, L1000_example.md. This check covers only the L prefix, three/four-digit number, underscore separator and .md extension. It does not validate snake_case titles, lesson contents, uniqueness or ID claims.
set -euo pipefail
# Count L-doc prefix/width matches (title conformance is not checked)
find .aget/evolution -type f \( -name "L[0-9][0-9][0-9]_*.md" -o -name "L[0-9][0-9][0-9][0-9]_*.md" \) | wc -l
# Find non-conforming files (excluding index.json)
find .aget/evolution -type f ! -name "L[0-9][0-9][0-9]_*.md" ! -name "L[0-9][0-9][0-9][0-9]_*.md" ! -name "index.json" ! -name "README.md"
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.
- 15d ago Changed 356459028658
- 1mo ago Changed · +27 lines 1e217e363ed1
- 1mo ago First seen · 134 lines · 34 tokens per session scan A 62225f596beb
aget-check-evolution is a skill published in the GitHub repository aget-framework/aget (12 stars, last pushed 7d ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,548 once invoked, about $0.0001 per session on Opus 5.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
aget-record-lesson
Record lessons learned from sessions as persistent, searchable, committable artifacts. Classifies each lesson as Framework (help other AGETs) or Domain (help principal).
aget-open-session
Open a session with context-aware establishment. Orchestrates wake-up, recovers prior session context, surfaces pending work, and proposes a session agenda.
aget-check-health
Run AGET health inspection and housekeeping checks. Detect-only — pair with /aget-enhance-health for remediation.
sivtr-memory
Retrieve shared local work memory: terminal activity, AI conversation history, prior decisions, validation evidence, debugging trails, recaps, and handoff context. Use before asking the user to repeat local work context.
memorywhale
Query and write durable debugging memory recorded by MemoryWhale. Use when debugging a failure that may have happened before, when you need the exact error/flags/output from an earlier attempt, when the user asks "how did we fix this last time?", or once you've figured out why something failed / how a fix worked and…
memorywhale-evidence
Use MemoryWhale debugging evidence when the user requests recall or a recurring failure may have relevant recorded history.