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-team-rolloutgit 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-team-rollout)<a href="https://agentmods.dev/skills/po4yka/llm-wiki-skills/llm-wiki-team-rollout"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-team-rollout/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-team-rollout"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-team-rollout.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.02123 |
| Opus 5 | $0.00037 | $0.01061 |
| Sonnet 5 | $0.00015 | $0.00425 |
| Haiku 4.5 | $0.00007 | $0.00212 |
Grade A, and why
llm-wiki-team-rollout 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM-Wiki Team Rollout
Goal
Introduce and operate LLM-Wiki in a team without creating an unreviewed official-looking slop layer or a hidden reliability burden.
Use references/docs/22-team-operating-model.md as the reference operating model for roles, RACI/DACI, governance, SLOs, rituals, staffing stages, dashboards, onboarding and GitOps controls.
When to use
- A team is adopting LLM-Wiki for the first time and needs an operating model, not just tooling.
- A pilot wiki is moving to early production and needs PR-based writes, CODEOWNERS and a review queue.
- Leadership asks for RACI/DACI, SLOs or a rollout plan before expanding to more domains.
- A team is deciding between read-only reports, PR-based writes, a draft wiki or direct writes.
- An existing rollout needs a governance or maturity-stage review (e.g. moving toward regulated/24x7).
Starter templates
Use these local templates when available:
references/templates/team-operating-model.yamlreferences/templates/team-raci-daci.yamlreferences/templates/team-review-workflow.yamlreferences/templates/team-slo-scorecard.yamlreferences/templates/team-onboarding-checklist.mdreferences/templates/CODEOWNERS.llm-wiki
Copy only the templates that fit the rollout stage, then replace placeholder roles, owners, SLOs and review-state gates.
Inputs
- Team size and workflows.
- Repository/docs platform.
- Existing docs, ADRs, onboarding material, issue/PR history, incident history and support channels.
- Security, privacy and permission constraints.
- Existing CODEOWNERS, branch protection and CI gates.
- Preferred write model: read-only, PR-based, direct writes, separate draft wiki.
- Current LLM-Wiki maturity: pilot, early production, business-critical, regulated/24x7.
- Desired outcome: adoption plan, operating model, RACI, templates, repo changes or governance review.
Procedure
1. Identify the organizational problem
Classify the primary use case:
- onboarding;
- bus factor / departing experts;
- agent context for coding workflows;
- decision provenance;
- incident/ops knowledge;
- product/research knowledge;
- customer/support knowledge;
- cross-team handoff;
- multi-domain knowledge governance;
- public/internal publishing;
- MCP/API/product interface support.
What ships with it
7 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.
- references/docs/22-team-operating-model.md 20 KB
- references/templates/CODEOWNERS.llm-wiki 2.2 KB
- references/templates/team-onboarding-checklist.md 2.5 KB
- references/templates/team-operating-model.yaml 3.5 KB
- references/templates/team-raci-daci.yaml 2.8 KB
- references/templates/team-review-workflow.yaml 2.7 KB
- references/templates/team-slo-scorecard.yaml 2.6 KB
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 · 292 lines · 74 tokens per session scan A 3676e8526df6
llm-wiki-team-rollout 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 2,123 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
wiki-fold
Roll up the wiki's journal.md entries into structured fold pages — like 2^k log compaction. Reads the last 2, 4, 8, 16... entries and writes a fold page that summarizes them by extractive summarization (no invention), with backlinks to children. Idempotent at the structural level — re-running with the same window…
decision-consolidate
Consolidate a SETTLED decision page (accepted / superseded / rejected — never proposed): compress the body to canon (verdict byte-intact, minimal why, alternatives as a table) and move the deliberation chronicle to a verified archives/ note (type: decision-archive) excluded from recall and search. Compress + archive…
moradin-forge
The Forge dispatcher. Reads a project's .forge/ state, tells the operator where they are, and routes to the right stage — full pipeline for new things, quick path for small changes, amendment when the plan changes. First run calibrates.
okf-pro
Operating rules for the .okf/ knowledge bundle — filing new concepts, the board, the journal, the daily snapshot, closing work, source attribution, and the generated/verified attestation policy. Use before reading from or writing anything into .okf/.
curate
Review pending Wenlan captures, revisions, or daemon refinements from Codex. Use for explicit audit walks after /brief or /handoff surfaces pending work. Invoked as /curate captures, /curate revisions, or /curate refinements.
prd-os
PRD creation and PRD execution operating system. Use when the founder asks to turn a rough idea into a PRD, run a Codex review on a PRD or issue, decompose an approved PRD into issue specs, or execute an issue with scope enforcement and receipt-based closeout. Not for general product ideation or casual drafting; this…