Borrowing it
Nothing to install: this file belongs to ptonlix/beeweave. 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/ptonlix/beeweave/main/.skills/wiki/beeweave-synthesize/SKILL.mdgit clone --depth 1 https://github.com/ptonlix/beeweaveWrote 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/ptonlix/beeweave/beeweave-synthesize)<a href="https://agentmods.dev/skills/ptonlix/beeweave/beeweave-synthesize"><img src="https://agentmods.dev/badge/skills/ptonlix/beeweave/beeweave-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/ptonlix/beeweave/beeweave-synthesize"><img src="https://agentmods.dev/badge/skills/ptonlix/beeweave/beeweave-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.00093 | $0.02186 |
| Opus 5 | $0.00046 | $0.01093 |
| Sonnet 5 | $0.00019 | $0.00437 |
| Haiku 4.5 | $0.00009 | $0.00219 |
Grade A, and why
beeweave-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 10d 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.
This is a copy
88% identical to wiki-synthesize — 19 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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 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
- Resolve config — follow the Config Resolution Protocol in
beeweave-core/SKILL.md(inline@nameoverride → walk up CWD for.env→~/.beeweave/config→ prompt setup). This givesBEEWEAVE_VAULT_PATHandBEEWEAVE_LINK_FORMAT(default:wikilink). - 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.
When writing internal links in synthesis pages, apply the link format from beeweave-core/SKILL.md (Link Format section) using the BEEWEAVE_LINK_FORMAT value.
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/*, _staging/*, _archives/*, legacy _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\]\]" "$BEEWEAVE_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.
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.
- 10d ago First seen · 210 lines · 93 tokens per session scan A 7abcf93c5f20
beeweave-synthesize is a skill published in the GitHub repository ptonlix/beeweave (6 stars, last pushed 1mo ago), licensed MIT. It adds 93 tokens to every session and 2,186 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to wiki-synthesize, differing in 19 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…