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 saski/arnesto --skill wiki-synthesizegit 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-synthesize)<a href="https://agentmods.dev/skills/saski/arnesto/wiki-synthesize"><img src="https://agentmods.dev/badge/skills/saski/arnesto/wiki-synthesize/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/saski/arnesto/wiki-synthesize"><img src="https://agentmods.dev/badge/skills/saski/arnesto/wiki-synthesize.svg" alt="Reviewed on agentmods" width="80" 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.01667 |
| Opus 5 | $0.00045 | $0.00834 |
| Sonnet 5 | $0.00018 | $0.00333 |
| Haiku 4.5 | $0.00009 | $0.00167 |
Grade A, and why
wiki-synthesize 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 5d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Synthesize — First-Class Synthesis Discovery
You are scanning the wiki for concepts that co-occur across many pages but have no dedicated synthesis page connecting them. Your job is to surface these gaps and fill the most valuable ones with cross-cutting synthesis pages.
Before You Start
- Read
~/.obsidian-wiki/config(preferred) or.env(fallback) to getOBSIDIAN_VAULT_PATH. - Read
index.mdto get the full page inventory. - Read
hot.mdif it exists — it surfaces recent activity and active threads that may already point to synthesis opportunities. - Read
_meta/taxonomy.mdto understand the tag vocabulary.
Step 1: Build the Co-occurrence Map
Scan every non-special page in the vault (skip index.md, log.md, hot.md, _insights.md, _meta/*, _archives/*, _raw/*).
For each page, collect:
- All
[[wikilinks]]it contains (outgoing links) - Its
tagsfrontmatter - Its
categoryfrontmatter
Build a co-occurrence matrix: for every pair of concept/entity pages (A, B), count how many other pages link to both A and B. This is their co-occurrence score.
You don't need to be exhaustive — aim for the top 20-30 pairs by co-occurrence score. Use Grep to find backlinks efficiently:
grep -rl "\[\[ConceptA\]\]" "$OBSIDIAN_VAULT_PATH" --include="*.md"
Run this for your top candidate concepts and intersect the result sets.
Step 2: Filter Out Already-Synthesized Pairs
Check the synthesis/ directory for existing pages. For each existing synthesis page:
- Read its
sourcesfrontmatter or its body for[[wikilinks]] - Mark those concept pairs as already covered
Remove covered pairs from your candidate list.
Step 3: Score and Rank Candidates
For each remaining candidate pair (or cluster of 3+), assign a synthesis value score:
| Signal | Points |
|---|---|
| Co-occurrence count ≥ 5 | +3 |
| Co-occurrence count 3-4 | +2 |
| Co-occurrence count 1-2 | +1 |
| Concepts are in different categories (cross-domain) | +2 |
| Concepts share tags but live in different folders | +1 |
One or both concepts are tagged as hubs in _insights.md |
+1 |
| A synthesis would resolve a flagged contradiction | +2 |
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.
- 5d ago First seen · 165 lines · 90 tokens per session scan A a2d8b07ca665
wiki-synthesize is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed 2d ago), licensed Unlicense. It adds 90 tokens to every session and 1,667 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
readonly-review
Run a no-network read-only review practice with two explorer steps and one synthesis step.
repo-harness-assessment
Use when evaluating repository agent-readiness, mapping harness roles, choosing the next smallest improvement, or designing and reconciling agent entrypoints such as AGENTS.md, CLAUDE.md, GEMINI.md, Cursor rules, or GitHub instructions.
work-state-and-delivery
Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
repo-contracts-and-boundaries
Use when turning architecture, layering, ownership, dependency direction, schemas, structural metrics, quality thresholds, baselines, allowlists, or generated quality snapshots into repository checks.
runtime-evidence-and-tracing
Use when connecting observed behavior, logs, metrics, request IDs, run IDs, screenshots, traces, external dependency results, or artifacts into a runtime evidence loop.
validation-harness-design
Use when designing repository validation commands, doctor scripts, test matrices, JSON or JUnit outputs, CI gates, smoke checks, or harness command surfaces.