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 agentmods add skills/odere-pro/claude-wiki-pages-plugin/engine-apinpx skills add odere-pro/claude-wiki-pages-plugin --skill engine-apigit 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/engine-api)<a href="https://agentmods.dev/skills/odere-pro/claude-wiki-pages-plugin/engine-api"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-wiki-pages-plugin/engine-api.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 | $0.00134 | $0.03640 |
| Opus 5 | $0.00067 | $0.01820 |
| Sonnet 5 | $0.00027 | $0.00728 |
| Haiku 4.5 | $0.00013 | $0.00364 |
Grade A, and why
engine-api 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 4d 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engine API — the deterministic tool surface
The engine is a Bun CLI invoked through scripts/engine.sh <command> [--target <vault>] [--json].
It is the source of truth for anything that must be exact (the wikilink graph,
frontmatter, MOC integrity). Agents call it and reason over its structured
output instead of eyeballing the vault. Always pass --json for machine use.
Invocation
bash "${CLAUDE_PLUGIN_ROOT}/scripts/engine.sh" <command> --target <vault> --json
Global flags:
--target <vault>— the vault root to operate on. Always supply this when a vault registry is configured; omitting it lets the engine resolve the vault independently, which may disagree with the hook's resolved path.--other-vaults <colon-separated-paths>— the registered vault roots other than the active one, used by thefirewallcommand to enforce thecross-vaultdeny rule. Derive this value fromregistry_other_vaultsinscripts/resolve-vault.shrather than hard-coding paths. See Multi-vault operating rules for the full confinement contract (ADR-0009 + ADR-0016).--json— emit structured JSON output. Always pass this for machine use.
If Bun is missing, the bridge prints a warning and exits 0 — degrade to the bash
verifiers (verify-ingest.sh) rather than failing.
Commands
verify — read-only integrity check
Ports verify-ingest.sh CHECK 0–3. Returns a report; exit 1 when any error, else 0.
{
"command": "verify",
"vault": "docs/vault",
"findings": [
{
"severity": "error|warn|info",
"check": "schema|index-duplicates|sources-format|moc|orphan-sources|topic-folder|legacy-index-filename",
"message": "…",
"file": "…"
}
],
"errors": 0,
"warnings": 0,
"clean": true
}
At schema_version 3 the per-folder index is a folder note (wiki/<topic>/<topic>.md,
type: index). A legacy _index.md is still accepted, but verify emits a
WARN-severity legacy-index-filename finding for it — message: run
engine.sh migrate --write. The WARN never flips clean to false on its own.
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.
- 4d ago First seen · 343 lines · 134 tokens per session scan A 48c584b9f1ac
engine-api is a skill published in the GitHub repository odere-pro/claude-wiki-pages-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 134 tokens to every session and 3,640 once invoked, about $0.0007 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
add-pdf-report
Internal implementation skill invoked by /add-native for app-generated PDF report workflows using expo-print and, when present, expo-sharing.
add-sharepoint
Adds SharePoint Online connector to a Power Apps code app. Use when reading lists, managing documents, or integrating with SharePoint sites. Can also create new SharePoint lists.
add-pdf-viewer
Internal implementation skill invoked by /add-native for native PDF control workflows. Handles HTTPS and file URI PDF viewing with @microsoft/power-apps-native-pdf-viewer 0.2.9+.
add-excel
Adds Excel Online (Business) connector to a Power Apps code app. Use when reading or writing Excel workbook data from OneDrive or SharePoint.
add-onedrive
Adds OneDrive for Business connector to a Power Apps code app. Use when uploading, downloading, listing, or managing files in OneDrive.
iso-24495-5
Provisional sector-specific Plain Language standard for document design (based on ISO/WD 24495-5, under development). Applied when structuring complex documents so readers can find and navigate content through layout, visual hierarchy, and navigation aids.