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 skills/agenttoolkit/altk-evolve/recallnpx skills add AgentToolkit/altk-evolve --skill recallgit clone --depth 1 https://github.com/AgentToolkit/altk-evolveWhat 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.00042 | $0.00817 |
| Opus 5 | $0.00021 | $0.00409 |
| Sonnet 5 | $0.00008 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
recall 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 2d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Entity Retrieval
Overview
This skill loads relevant stored Evolve entities into the current turn before substantive work begins.
Use this skill first whenever the task involves:
- code changes
- debugging
- code review
- repo exploration
- file inspection
- environment/tooling investigation
Skip only for trivial conversational requests with no local context.
Required Action
Before any non-trivial local work, you must complete the recall workflow below. Reading this SKILL.md alone does not satisfy the skill.
Completion Rule
Do not proceed to other analysis or tool use until all steps below are complete.
- If a manifest has already been injected for this turn, use it to pick which entity files to open. Otherwise inspect
${EVOLVE_DIR:-.evolve}/entities/and${EVOLVE_DIR:-.evolve}/public/for guidance relevant to the current task. - Read each matching entity file that appears relevant.
- Summarize the applicable guidance in your own words before proceeding.
- If no relevant entities exist, state that explicitly before proceeding.
Required Visible Completion Note
Before moving on, produce an explicit completion note in your reasoning or user update using one of these forms:
Recall complete: searched ${EVOLVE_DIR:-.evolve}/entities/, read <files>, applicable guidance: <summary>Recall complete: searched ${EVOLVE_DIR:-.evolve}/entities/, no relevant entities found
Minimum Acceptable Procedure
- List or search files under
${EVOLVE_DIR:-.evolve}/entities/and${EVOLVE_DIR:-.evolve}/public/(or read the injected manifest if one is present). - Identify candidate entities relevant to the task.
- Open and read those entity files.
- Summarize what applies, or state that nothing applies.
Failure Conditions
The skill is not complete if any of the following are true:
- You only read this
SKILL.md - You did not inspect
${EVOLVE_DIR:-.evolve}/entities/ - You did not read the relevant entity files
- You proceeded without stating whether guidance was found
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 101 lines · 42 tokens per session scan A 5ce395bc2bd5
recall is a skill published in the GitHub repository AgentToolkit/altk-evolve (105 stars, last pushed 7d ago), licensed Apache-2.0. It adds 42 tokens to every session and 817 once invoked, about $0.0002 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
agent-recall
Persistent compounding memory for AI agents. 5 default MCP tools: sessionstart, sessionend, remember, recall, check. Full surface (18 tools) available with --full flag. Two-verb model: inhale (sessionstart) and exhale (sessionend). Correction-first memory with decision trail tracking, watchfor warnings, palace rooms…
shelve
Offload a closed conversation topic (or a whole imported dialog) to the memory shelf as a Markdown episode with a validated digest. Use when a topic is finished, when context grows heavy, before compaction, or when the user asks to shelve/archive part of the conversation. M0 prompt-only version — the agent does the…
speckit-tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
speckit-clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
speckit-implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit-taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.