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 aget-framework/template-advisor-aget --skill aget-check-evolutiongit clone --depth 1 https://github.com/aget-framework/template-advisor-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/template-advisor-aget/aget-check-evolution)<a href="https://agentmods.dev/skills/aget-framework/template-advisor-aget/aget-check-evolution"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-check-evolution.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.00034 | $0.00936 |
| Opus 5 | $0.00017 | $0.00468 |
| Sonnet 5 | $0.00007 | $0.00187 |
| Haiku 4.5 | $0.00003 | $0.00094 |
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 7d 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.
This is a copy
100% identical to aget-check-evolution — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 134 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:
1. File Inventory
# 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
Valid L-doc pattern: L###_*.md (e.g., L588_skill_invocation_control_semantics.md)
# Count valid L-doc names
find .aget/evolution -type f -name "L[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 "index.json" ! -name "README.md"
3. Disk Usage
du -sh .aget/evolution
4. Index Integrity
Check that index.json exists and is valid JSON:
test -f .aget/evolution/index.json && jq empty .aget/evolution/index.json 2>/dev/null && echo "valid" || echo "invalid"
Thresholds
| Metric | OK | WARN | CRITICAL |
|---|---|---|---|
| Total files | <500 | 500-750 | >750 |
| Non-standard files | 0-10 | 11-50 | >50 |
| Disk size | <10MB | 10-25MB | >25MB |
| Index integrity | valid | - | invalid |
Note: Thresholds inherited from supervisor defaults. Research AGET baseline (2026-02-08): 94 files, 800K - well within OK range.
Output Format
Report the following:
=== /aget-check-evolution ===
Directory: .aget/evolution/
File Counts:
Total: [count]
L-docs: [count] (.md matching L###_*.md)
Index: [1 if exists, 0 otherwise]
Other: [count] (non-conforming)
Disk Usage: [size]
Index Status: [valid/invalid/missing]
Non-Conforming Files:
[list any files not matching expected patterns]
Health Status: [OK | WARN | CRITICAL]
Alerts:
[list any threshold violations]
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.
- 7d 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/template-advisor-aget (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 34 tokens to every session and 936 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to aget-check-evolution, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
pipefy-skill-template
Copy this file when authoring a new Pipefy skill. Replace placeholders, then rename the folder so it matches the frontmatter name.
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.