Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/AgentToolkit/altk-evolvenpx agentmods add skills/agenttoolkit/altk-evolve/agent-wiki-synthesize-skillWrote 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/agenttoolkit/altk-evolve/agent-wiki-synthesize-skill)<a href="https://agentmods.dev/skills/agenttoolkit/altk-evolve/agent-wiki-synthesize-skill"><img src="https://agentmods.dev/badge/skills/agenttoolkit/altk-evolve/agent-wiki-synthesize-skill.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.00056 | $0.02437 |
| Opus 5 | $0.00028 | $0.01218 |
| Sonnet 5 | $0.00011 | $0.00487 |
| Haiku 4.5 | $0.00006 | $0.00244 |
Grade A, and why
agent-wiki-synthesize-skill 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.
How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Wiki — Synthesize Skill
Overview
Promote a successful workflow from a saved trajectory into an executable
agent skill living inside a wiki at <wiki>/skills/<slug>/SKILL.md. The
output is the procedural counterpart to agent-wiki-extract-guidelines's
declarative pages: a guideline tells a future agent what to do; a synthesized
skill is a structured workflow page the future agent can read and execute
directly, optionally invoking sibling scripts via Bash.
This is the per-trajectory promote-to-procedural pass of the agent-wiki
family. Run it after one or more trajectories captured the same recipe and
you want future agents to invoke that recipe instead of re-deriving it.
Ingesting a whole batch end-to-end? Prefer the
agent-wiki-ingestskill, which sequences summarize → extract → synthesize → consolidate → catalog. It runs this skill at the right point (after extraction, before consolidation) and guarantees the consolidation pass that clusters the surviving atomics is never skipped. Use this standalone skill only to promote a single trajectory's workflow.
When To Use
Use this skill when a trajectory captured:
- A non-trivial successful workflow — multiple tool calls, with at least one custom script or non-obvious sequence — that produced the answer after trial-and-error. The eventual happy path is worth saving.
- A reusable command sequence or script the agent wrote. Particularly if the agent had to reconstruct it across multiple attempts.
- A pattern a future agent will hit on a similar-but-not-identical task — parsing a binary format, walking a structured directory, reaching a specific tool fallback.
Skip this skill — let agent-wiki-extract-guidelines cover the case with a
guideline alone — when:
- The workflow is a single trivial command (
grep -c TODO ...). - The path embeds secrets, tokens, or one-off user inputs.
- A skill with the same trigger already exists in
<wiki>/skills/. - The session ended without reaching a clear successful answer.
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 · 268 lines · 56 tokens per session scan A 739a0d1a58a5
agent-wiki-synthesize-skill is a skill published in the GitHub repository AgentToolkit/altk-evolve (105 stars, last pushed 4d ago), licensed Apache-2.0. It adds 56 tokens to every session and 2,437 once invoked, about $0.0003 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
memory-to-skill
Turn workflows from your MemSearch memory into reusable skills. Use when the user asks to make/create/extract/distill a skill from what they just did or from past work, review skill candidates, install a distilled skill, or 'turn this into a skill'. Manages MemSearch procedural-memory candidates under…
media-gen
Photoreal image + video generation and upscaling via fal.ai (pay-per-use, one API key, always-current models: Kling, Seedance, FLUX, nano-banana Pro, Topaz). Use for image-to-video ("animate this image", "turn this photo into a video"), photoreal video clips for websites/demos, hero video loops, upscaling…
research-notebook
Deep research on any topic via the NotebookLM CLI. Use whenever the user requests research on a topic, in any project, in any language. Triggers on phrases like "research this", "deep dive on", "do research on", "dig into", "find out about", "investigate", "look into", "research X for me". Creates or reuses a…
learn
Use when the user shares a conclusion, note, or takeaway from something they're studying — a book, course, or article — and wants it captured into their personal learning archive. Trigger phrases include "what I learned today", "notes from the book", "conclusions from chapter X", plus the explicit /learn command. Also…
wiki-article
Write a wiki article capturing structure you learned about an active project in the user's hub. Use when you grepped or spawned Explore agents to understand a project and must record that knowledge before /done, or when the user asks to "write a wiki article", "document this in the wiki", or "add this to the wiki".
captain-recall
Use when the user asks WHY or WHAT-HAPPENED questions about this system — historical decisions, past incidents, why code/config is shaped a certain way, where something is deployed, who decided what, or the state of work in flight. Queries the tsubasa knowledge graph for cited answers.