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 odere-pro/claude-wiki-pages-plugin --skill fixgit clone --depth 1 https://github.com/odere-pro/claude-wiki-pages-pluginWrote 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/odere-pro/claude-wiki-pages-plugin/fix)<a href="https://agentmods.dev/skills/odere-pro/claude-wiki-pages-plugin/fix"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-wiki-pages-plugin/fix.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.00080 | $0.01243 |
| Opus 5 | $0.00040 | $0.00622 |
| Sonnet 5 | $0.00016 | $0.00249 |
| Haiku 4.5 | $0.00008 | $0.00124 |
Grade A, and why
fix 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 7d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM Wiki — Fix
Apply the repairs /claude-wiki-pages:lint identified.
When to invoke
- The user has just run lint and asks to fix what it found.
- The
claude-wiki-pages-curator-agentagent is orchestrating the lint → fix → lint cycle. - The user is confident enough to fix without a prior lint pass (in which case this skill runs lint internally first).
Inputs
One of:
- A recent lint report in conversation context.
- A fresh lint pass run internally (no report in context).
In both cases, the schema (vault/CLAUDE.md) is read first.
Reading contract
vault/CLAUDE.md— the schema.vault/wiki/**/*.md— every wiki page that a lint rule flagged.- The lint report, when provided.
Writing contract
Writes are confined to what the specific lint finding authorizes:
| Finding | Repair |
|---|---|
| Missing required frontmatter | Backfill with the schema default. If no sane default exists, escalate to the user. |
| Dangling wikilink | Replace with the nearest matching alias; or comment out with <!-- unresolved: ... --> and flag as a remaining warning. |
Plain-string sources: entry |
Convert to [[wikilink]] if the matching source page exists; otherwise leave and flag. |
Missing parent / path |
Derive from file location under wiki/. |
| MOC missing member | Add the page or subfolder to children: / child_indexes: of its per-folder MOC (the folder note <folder>/<folder>.md, or legacy _index.md if present), as quoted "[[wikilink]]" entries. |
| Missing per-folder MOC | Create the folder note at its canonical name <folder>/<folder>.md (type: index). Never create a new _index.md. |
Legacy index filename (legacy-index-filename WARN) |
Leave in place — this skill never renames an existing _index.md; the rename is engine.sh migrate --write's job. Reconcile its fields like any folder note. |
| Banned legacy value | Rewrite: type: moc → type: index; _MOC.md → the folder-note name; child_mocs: → child_indexes:. |
Strict-tree drift (non-spine / cross-tree edge / cycle, tree-lint ADR-0036) |
Run bash scripts/strict-tree-reduce.sh --target <vault> --apply (git-checkpointed) — it demotes every non-spine [[wikilink]] to prose and adds topic/<tree> de-cycle tags so the graph draws only the parent: spine. A deterministic graph-shape repair, not a per-page edit; never hand-rewrite links to fake conformance. Detect first with bash scripts/tree-lint.sh --target <vault>. |
| Vault MOC drift | Escalate to /claude-wiki-pages:index; do not edit wiki/index.md directly. |
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.
- 7d ago First seen · 114 lines · 80 tokens per session scan A 5b513561fa6b
fix is a skill published in the GitHub repository odere-pro/claude-wiki-pages-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 80 tokens to every session and 1,243 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
upstream-tracker
Manage upstream issue tracking for this project. Use when the user wants to log a bug or friction point in a vendor package or npm dependency, review open upstream items, resolve a tracked issue, run a trend review, generate the upstream observations section of a sprint retrospective, promote upstream observations to…
audit-ppmplugin
Statically audit a built .ppmplugin before wrap testing. Checks archive layout, manifest compatibility, bundle consistency, Android DEX integrity and SDK leakage, iOS framework structure, native source-to-receiver alignment, and the PCF composite-key/sendAsync transport contract. Reports CRITICAL, WARNING, and INFO…
debug-extension
Diagnose and fix failures in a built third-party .ppmplugin control: crashes, silent no-ops, PCF error outputs, or incorrect behavior. Uses the reported symptom, shared/error-codes.md, and file-level evidence to trace the manifest, Android/iOS modules, PCF dispatch, and build configuration. Produces a ranked…
generate-ppmplugin-manifest
Validate, reconcile to the chosen target(s), and stage the manifest.json for a .ppmplugin bundle. In the normal flow the committed ./manifest.json already exists (authored by /generate-native-extension), so this stage reads it, runs the plugin's upload-compatibility checks locally as a pre-flight gate (name regex…
diagnose-deployment
Surfaces PAC CLI upload errors and Dataverse async operation errors, pattern-matches against a known failure catalog, and optionally auto-fixes identified issues. Use when asked to: "diagnose deployment", "debug deployment", "deployment failed", "show deployment errors", "fix deployment issues", "show upload logs"…
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.