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 theafh/ai-modules --skill wiki_wrapupgit clone --depth 1 https://github.com/theafh/ai-modulesWrote 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/theafh/ai-modules/wiki_wrapup)<a href="https://agentmods.dev/skills/theafh/ai-modules/wiki_wrapup"><img src="https://agentmods.dev/badge/skills/theafh/ai-modules/wiki_wrapup/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/theafh/ai-modules/wiki_wrapup"><img src="https://agentmods.dev/badge/skills/theafh/ai-modules/wiki_wrapup.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.00100 | $0.01213 |
| Opus 5.5 | $0.00040 | $0.00485 |
| Sonnet 5.5 | $0.00020 | $0.00243 |
| Haiku 4.5 | $0.00010 | $0.00121 |
Grade A, and why
wiki_wrapup 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 1mo 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wiki_wrapup
<wiki_wrapup>
Session-to-wiki reconciliation editor. Mine the active chat for durable knowledge, diff against the wiki, and triage the result before any write.
<orient_first_top>Read $WIKI/SCHEMA.md once at the start of any session that activates this skill. The schema declares the domain, page-type enum, tag taxonomy, and conventions every candidate must be classified against. The full orientation pass (SCHEMA + index + recent log) is covered by <orient_first> in <policy> below; this top-line note exists so the SCHEMA read is never skipped on a "quick" wrap-up.</orient_first_top>
Identify what the session produced that does not yet live in the wiki, surface conflicts between session content and wiki content, and propose reconciliations the user can accept page by page. Defer all wiki structure, discovery, orientation, ingest, and lint behavior to the wiki skill.
<resolve_skill_bundle>Resolve $WIKI_SKILL before the first bundled tool call and before $WIKI. It is the installed wiki skill bundle holding the scripts this skill invokes. The wiki skill's <resolve_wiki_skill_bundle> block is the canonical resolution order, so follow it rather than guessing a path. From this skill's own directory the sibling hub is ../wiki. Every $WIKI_SKILL/... path below resolves through that block.</resolve_skill_bundle>
<resolve_first>Resolve $WIKI through the wiki skill's discovery flow before reading the session. Honor exit-2 ambiguity by presenting candidates and asking the user.</resolve_first>
<orient_first>Read SCHEMA.md, index.md, and roughly the last 350 lines of log.md before diffing, so the diff runs against an understood corpus.</orient_first>
<mine_session>Extract durable claims, decisions, definitions, conventions, comparisons, workflows, and named entities. Skip abandoned hypotheses, transient back-and-forth, and user-private ephemera.</mine_session>
For each candidate, pick a page type from the wiki skill's enum and tag it NEW, EXTEND, CONFIRM, or CONFLICT against $WIKI.
<surface_contradictions>For every CONFLICT, capture both excerpts verbatim, name the disagreement dimension (factual / definitional / scope / recency / source-quality), and offer two or three concrete reconciliation paths.</surface_contradictions>
<propose_then_act>Emit the proposal and wait for user selections before any write. Skip CONFIRM entries from the proposal unless the user asked for a full inventory.</propose_then_act>
<defer_writes>Route approved NEW and EXTEND items through the wiki skill's Ingest flow. Route approved CONFLICT items through its contested-page protocol (contested: true, contradictions: frontmatter, both positions recorded with dates and sources).</defer_writes>
<session_only>Source material is the visible session only. Skip claims the session did not establish.</session_only>
Run "$WIKI_SKILL/scripts/discover_wiki.sh" and resolve $WIKI. On exit 2, present candidates in walk order and stop until the user picks.
Read SCHEMA.md, index.md, and roughly the last 350 lines of log.md.
Walk the session top to bottom. Build a list of durable items, each with title, suggested page type, target slug, and source-message reference.
Search $WIKI for each item. Tag NEW, EXTEND, CONFIRM, or CONFLICT. For CONFLICT items, capture both excerpts.
Emit one report under three H2 headings: ## New pages, ## Extensions to existing pages, ## Contradictions to reconcile.
On approval, route each item through the wiki skill's matching flow, run python3 "$WIKI_SKILL/scripts/lint.py", and append a single ## [YYYY-MM-DD HH:MM] session-wrapup | N new, N extended, N contested entry to log.md listing only files actually changed.
<output_contract>
<proposal_format>Three H2 sections. Each entry: title, suggested type, target path, source-message reference. Contradictions also carry wiki excerpt, session excerpt, disagreement dimension, and ≥2 reconciliation options.</proposal_format>
<no_writes_before_approval>Skip every wiki write during the proposal phase.</no_writes_before_approval>
<log_entry>One dated session-wrapup entry that lists only files actually created or updated.</log_entry>
Every candidate carries type and target; every CONFLICT carries both excerpts and ≥2 reconciliation options; no wiki file is modified before approval; the log entry matches actual file changes.
</output_contract>
</wiki_wrapup>
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.
- 1mo ago Changed eae4f7f3b0e6
- 1mo ago First seen · 41 lines · 100 tokens per session scan A 9c5de645472c
wiki_wrapup is a skill published in the GitHub repository theafh/ai-modules (38 stars, last pushed today), licensed MIT. It adds 100 tokens to every session and 1,213 once invoked, about $0.0004 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
apify-youtube-transcript-scraper
Get YouTube captions, timestamped quotations, SRT/VTT and translated transcripts for videos, channels and playlists through the harshmaur/youtube-transcript-scraper Apify Actor.
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
baoyu-youtube-transcript
A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.