Borrowing it
Nothing to install: this file belongs to saski/arnesto. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/saski/arnesto/main/.agents/skills/wiki-capture/SKILL.mdgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/wiki-capture)<a href="https://agentmods.dev/skills/saski/arnesto/wiki-capture"><img src="https://agentmods.dev/badge/skills/saski/arnesto/wiki-capture.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.00090 | $0.01519 |
| Opus 5 | $0.00045 | $0.00759 |
| Sonnet 5 | $0.00018 | $0.00304 |
| Haiku 4.5 | $0.00009 | $0.00152 |
Grade A, and why
wiki-capture 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 3d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Capture — Conversation to Wiki Note
You are preserving knowledge from the current conversation as a permanent wiki note. The goal is to extract the substance — the knowledge itself — not a summary of what was said.
Before You Start
- Read
~/.obsidian-wiki/config(preferred) or.env(fallback) to getOBSIDIAN_VAULT_PATH - Read
$OBSIDIAN_VAULT_PATH/index.mdto understand existing wiki content (avoid duplicates) - Read
$OBSIDIAN_VAULT_PATH/hot.mdif it exists — it gives context on recent activity
Step 1: Identify What's Worth Preserving
Scan the conversation. Ask: what knowledge emerged here that would be valuable in 3 months with no memory of this chat?
Worth preserving:
- Decisions made and why they were made
- Analysis, frameworks, mental models developed
- Technical findings, patterns, or procedures
- Synthesized understanding of a topic
- Clear explanations of a concept that took effort to arrive at
- Key facts from an external source discussed in the conversation
Skip:
- Logistics, scheduling, pleasantries
- Exploratory back-and-forth where no conclusion was reached
- Content that's already in the wiki
If nothing material emerged, tell the user and stop.
Step 2: Classify the Content Type
Assign one of five types — this determines the target folder and tone:
| Type | Description | Target folder |
|---|---|---|
synthesis |
Multi-step analysis or an answer to a specific question that required reasoning | synthesis/ |
concept |
A definition, framework, or mental model (what a thing is) | concepts/ |
source |
Summary of an external document, article, or resource discussed | references/ |
decision |
A strategic, architectural, or design choice and its rationale | synthesis/ |
session |
A complete discussion summary when the conversation spans multiple topics | journal/ |
If the content clearly belongs to a specific project (detected from context or user mention), place it under projects/<project-name>/<category>/ instead.
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.
- 3d ago First seen · 210 lines · 90 tokens per session scan A 39b7a8db54a2
wiki-capture is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed today), licensed Unlicense. It adds 90 tokens to every session and 1,519 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
immune
Hybrid adaptive memory: Cheatsheet (positive patterns pre-generation) and Immune (negative patterns post-generation) with Hot/Cold tiered auto-learning. Triggers on: "scan for errors", "immune scan", "check output quality", "antibody scan". NOT for PR review (use pr-review) or repo audits (use repo-sentinel).
usage-audit
Audit a Claude Code setup for token waste and context bloat. Checks MCP servers, CLAUDE.md, skills, and settings against bloat filters. Triggers on: "audit my context", "usage audit", "token audit", "context bloat". NOT for codebase audits.
brain-ingest
The process for digesting a conversation, document, or research result, classifying it, and writing it down as brain content (a root-page update or a new/updated page) through the brain CLI.
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
agentic-os
A design for running persistent specialist agents, commands, scripts, and file-based memory inside Codex. It keeps the setup in project files so it can continue across sessions.
memory-and-handoff
Two-mode skill: (1) session memory — load/persist durable workflow state under .cc10x/ (activeContext, patterns, progress) so context survives compaction; (2) handoff package — portable, secrets-redacted export for a coworker, different tool, or fresh non-cc10x session.