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 statusgit 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/status)<a href="https://agentmods.dev/skills/odere-pro/claude-wiki-pages-plugin/status"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-wiki-pages-plugin/status/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/odere-pro/claude-wiki-pages-plugin/status"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-wiki-pages-plugin/status.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.00081 | $0.00928 |
| Opus 5 | $0.00041 | $0.00464 |
| Sonnet 5 | $0.00016 | $0.00186 |
| Haiku 4.5 | $0.00008 | $0.00093 |
Grade A, and why
status 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 8d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM Wiki — Status
Confirm every piece of Layer 4 orchestration is wired and fires. Leave the vault exactly as you found it.
This skill answers the question: "If I ran the pipeline right now, which hooks would fire and which would silently skip?"
When to invoke
- Immediately after installing the plugin — verify the install.
- After editing hooks or scripts — verify the edit.
- When the user suspects a hook is not firing (e.g., frontmatter violations slip through).
- Periodically, as a smoke test.
Reading contract
hooks/hooks.json— the hook wiring manifest.- Every script referenced from
hooks/hooks.json— confirm executable, valid shell, returns expected exit codes for synthetic inputs. vault/CLAUDE.md— the schema, to construct valid and invalid test payloads.- The user's project tree — only to determine the vault path; never its contents.
Writing contract
Zero writes to vault/. Specifically:
- No log append (this skill is a diagnostic; logging health checks clutters the log).
- No scratch files under
vault/. - Transient test payloads may be constructed in a tempdir outside
vault/(e.g.,$TMPDIR) and must be removed before the skill returns.
The skill enforces its own non-mutation invariant: compare git status vault/ (or a checksum of vault/) before and after; any diff is a skill
bug and must be surfaced as a FAIL.
Workflow
Run these checks in order. Each produces one line in the report.
- Dependency check.
jq,bash >= 3.2, every hook script readable and executable. SessionStartpreamble. Synthesize a session open; confirm the schema-reminder preamble is printed.PreToolUsefrontmatter gate. Attempt a synthetic Write with malformed frontmatter; confirm exit code 2.PreToolUseraw-immutability gate. Attempt a synthetic Write undervault/raw/; confirm exit code 2.PreToolUsewikilink gate. Attempt a synthetic Write that uses a markdown link where a wikilink is required; confirm exit code 2.PreToolUseattachment gate. Attempt a synthetic source-page Write with a missingattachment_path; confirm exit code 2.PostToolUsereminder. Perform a read-only synthesis of a wiki write; confirm the index-reminder message appears.SubagentStopingest gate. Simulate the completion of an ingest agent; confirmverify-ingest.shruns.SubagentStoplint gate. Simulate the completion of a lint-fix agent; confirm the lint gate runs.- Schema read. Confirm
vault/CLAUDE.mdparses as YAML frontmatter- markdown,
schema_versionis an integer, and the plugin supports it.
- markdown,
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.
- 8d ago First seen · 110 lines · 81 tokens per session scan A 940def62e208
status is a skill published in the GitHub repository odere-pro/claude-wiki-pages-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 81 tokens to every session and 928 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…
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…
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…
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"…
debug-flow
Debug a failed Power Automate flow run. Use when a flow failed, has errors, or the user wants to troubleshoot a run.