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 po4yka/llm-wiki-skills --skill llm-wiki-paf-adoptiongit clone --depth 1 https://github.com/po4yka/llm-wiki-skillsWrote 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/po4yka/llm-wiki-skills/llm-wiki-paf-adoption)<a href="https://agentmods.dev/skills/po4yka/llm-wiki-skills/llm-wiki-paf-adoption"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-paf-adoption/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/po4yka/llm-wiki-skills/llm-wiki-paf-adoption"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-paf-adoption.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.00074 | $0.01587 |
| Opus 5 | $0.00037 | $0.00794 |
| Sonnet 5 | $0.00015 | $0.00317 |
| Haiku 4.5 | $0.00007 | $0.00159 |
Grade A, and why
llm-wiki-paf-adoption 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 12d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM-Wiki PAF Adoption
Goal
Help users reason about LLM-Wiki as a possible technical substrate for PAF Nexus/Cortex adoption without collapsing the product-management framework into a generic wiki.
When to use
Use when the user asks:
- "Is LLM-Wiki basically Nexus and Cortex?"
- "Am I oversimplifying PAF by mapping Nexus to wiki and Cortex to agents?"
- "Which Nexus should we start with: market, product, growth, company?"
- "How do we make this shared at company level, not personal or single-team?"
- "How do we check that it affects decisions rather than becoming another docs dump?"
- "What can we reuse from LLM-Wiki skills, and what must be built for PAF?"
- "How do Product Engineer / Product Ops roles map to LLM-Wiki ownership?"
Inputs
- The user's question about mapping LLM-Wiki to PAF concepts (Nexus, Cortex, Product Engineer, Product Ops, Context Ripeness, Confidence Point).
- Any PAF source page or citation the user provides, when the claim involves a current or source-specific PAF definition.
- The user's current adoption stage: still weighing the analogy, choosing a first Nexus, or already running a pilot.
- Whether the target scope is company-level, single-team, or personal adoption.
- The reference docs listed under "Required references", when present in the repo.
Required references
Read these when available:
references/docs/paf-nexus-cortex.mdskills/llm-wiki-faq/references/additional-adoption-q-and-a.mdreferences/docs/adoption-objections.mdreferences/docs/adoption-q-and-a.md
For PAF source claims, browse and cite the current Product Framework page or the specific PAF source the user provides.
Core stance
Use this answer:
LLM-Wiki can be the technical skeleton of a Nexus, and Agent Skills/workflows can be an early Cortex. But this is only true after you add PAF-specific object boundaries, node schema, ownership, confidence/ripeness metrics, decision loops and company governance. A Markdown wiki by itself is not a Nexus; a chatbot by itself is not a Cortex.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 193 lines · 74 tokens per session scan A 083bff358ab9
llm-wiki-paf-adoption is a skill published in the GitHub repository po4yka/llm-wiki-skills (3 stars, last pushed 19d ago), licensed MIT. It adds 74 tokens to every session and 1,587 once invoked, about $0.0004 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-31.
Other skills, from other repositories
okf-harness-bootstrap
This unified entrypoint routes setup and workspace maintenance without making the user choose a mode.
okf-harness
One Door routes OKF Harness workspace requests to exactly one internal workflow at a time.
wiki-lint
Health-check a wiki vault. Finds orphan pages (no inbound links), dead wikilinks (point to non-existent pages), missing frontmatter fields, stale claims, empty sections, and pages absent from catalog.md. Produces a structured report with severity tiers and proposes concrete fixes — but does not auto-apply them unless…
meta-sync-template
Interactive flow to propagate the reference (.template) vault's plugins, snippets, and root docs to one or more configured vaults. Reads the active router config, lists every vault with online status, flags vaults missing obsidian-local-rest-api upfront, lets the user pick all or a subset, and optionally re-clones…
save
File the current Claude conversation (or a specific insight from it) as a structured wiki note. Auto-detects the right type (decision, answer, session-log, technique, ADR), writes appropriate frontmatter, places the file in the correct wiki folder, and updates catalog.md, journal.md, hot.md. Use when the user says…
wiki-boundary
Rank the "frontier" pages of a wiki — the crossroads many pages link to that stay thin inside — so you can decide where research would pay off most. Use when the user says "what should I write about next", "where are the gaps", "which pages need work", "find the thin hub pages", "boundary pages", "/wiki-boundary"…