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/agent-wiki-consultnpx skills add AgentToolkit/altk-evolve --skill agent-wiki-consultgit clone --depth 1 https://github.com/AgentToolkit/altk-evolveWrote 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-consult)<a href="https://agentmods.dev/skills/agenttoolkit/altk-evolve/agent-wiki-consult"><img src="https://agentmods.dev/badge/skills/agenttoolkit/altk-evolve/agent-wiki-consult.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 | $0.00055 | $0.01043 |
| Opus 5 | $0.00028 | $0.00522 |
| Sonnet 5 | $0.00011 | $0.00209 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
agent-wiki-consult 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 4d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Wiki — Consult
Overview
This skill is a thin wrapper around the wiki's own AGENTS.md document. The
wiki contains evidence-grounded guidelines distilled from agent
trajectories; AGENTS.md is its agent-readable contract for navigation
and retrieval. This skill tells you to:
- Find the wiki root.
- Read
<wiki-root>/AGENTS.md. - Follow the recipe described there against the user's current task.
The retrieval logic lives in AGENTS.md, not in this skill. That separation
is intentional: when the wiki's structure or recall heuristics change, edit
AGENTS.md and not this skill.
When to invoke
Call this skill once you know the task or sub-task you're about to do. Concretely:
- After the user has stated their request and you have a plan for the next block of work.
- Before writing non-trivial code in a problem space the wiki may have documented.
- Mid-task when a new sub-task emerges with its own narrow scope (e.g. "now I need to handle browser auth resumption").
Do not invoke at session start (no task to filter against), and do not invoke for trivial tasks (typo fix, single-line edit) where the wiki's overhead exceeds the work.
Workflow
Step 1: Resolve the wiki root
If the user passed a path argument (e.g. wiki-twobatch,
wiki-twobatch-skills, or any other path), use it.
Otherwise auto-detect: walk up from the current working directory looking
for any sibling directory matching wiki-* that contains an _config.yaml
file. If multiple are found, prefer the one closest to cwd. If none are
found, ask the user which wiki to consult.
Step 2: Read AGENTS.md
Read <wiki-root>/AGENTS.md
This is the contract document. It explains the wiki's structure, the
filename suffix convention, the _index.jsonl schema, and a recommended
retrieval recipe. Read it in full — it's typically 3–5 KB.
If the file does not exist, run:
uv run python explorations/agent-wiki/skills/scripts/build_agent_wiki.py \
--wiki-root <wiki-root> catalog
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.
- 4d ago First seen · 125 lines · 55 tokens per session scan A 46c58cba8dca
agent-wiki-consult is a skill published in the GitHub repository AgentToolkit/altk-evolve (105 stars, last pushed yesterday), licensed Apache-2.0. It adds 55 tokens to every session and 1,043 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…
memory-recall
Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this…
memesh-review
Review and optimize the MeMesh memory database. Analyzes health score, finds stale/conflicting/redundant memories, shows work patterns, and suggests cleanup actions. Use when asked to "review memories", "check memory health", "clean up knowledge", or "what's in my memory".
elicit
Form-driven Socratic discovery — batch independent decision dimensions into one multi-select-capable form instead of N button-turns. Triggers on: scope this, discovery form, ask me everything at once, multi-select question.
roundtable
Convene the multi-LLM round table — Claude, Antigravity, and Codex deliberate a question; the user chairs promotion. Triggers on: roundtable, round table, convene the table, ask the table, what do the other models think, deliberate.
author-feature
Author a single-source feature page — a code-verified master that projects to .help kinds + docs pages, no API credits. Triggers on: author a feature page, single-source doc, new feature master, draft docs without an api.