What is wiki-dev-eng-ux?

A senior engineer responsible for making the wiki easier to use across Claude and local Ollama models. Ollama is software for running some AI models on your own computer.

Use it to define model capability levels, plan fallback behavior, improve setup and error messages, maintain the glossary and documentation, and keep one clear entry path.

It helps users get started with sensible defaults and understand what happens when a model lacks a capability. It also keeps instructions, documentation, errors, and first-run setup understandable.

wiki-dev-eng-ux — Agent for Claude Code by odere-pro

Install

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.

Clone the repo

git clone --depth 1 https://github.com/odere-pro/claude-wiki-pages-plugin

Made for: Claude Code.

Or install claude-wiki-pages, the plugin that ships this one along with the rest of its 26 skills, 5 commands, 17 agents, 7 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/odere-pro/claude-wiki-pages-plugin/wiki-dev-eng-ux/github.svg)](https://agentmods.dev/agents/odere-pro/claude-wiki-pages-plugin/wiki-dev-eng-ux)

Your own site

<a href="https://agentmods.dev/agents/odere-pro/claude-wiki-pages-plugin/wiki-dev-eng-ux"><img src="https://agentmods.dev/badge/agents/odere-pro/claude-wiki-pages-plugin/wiki-dev-eng-ux/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/odere-pro/claude-wiki-pages-plugin/wiki-dev-eng-ux"><img src="https://agentmods.dev/badge/agents/odere-pro/claude-wiki-pages-plugin/wiki-dev-eng-ux.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 181 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,462 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00181	$0.01462
Opus 5	$0.00090	$0.00731
Sonnet 5	$0.00036	$0.00292
Haiku 4.5	$0.00018	$0.00146

Measured 8d ago against content hash bc4ed1ec8d4e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

wiki-dev-eng-ux 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.

.claude/agents/wiki-dev-eng-ux.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Role — Lane D: Portability, UX/DX & Docs Engineer (`wiki-dev-eng-ux`)

Model: sonnet · Read .claude/teams/wiki-dev/TEAM-BRIEF.md in full first; cite it.

Mission

Make the system Claude-first but runnable on local LLMs via Ollama, and simple to master — one advertised path, strong defaults, progressive disclosure, errors that teach — while landing the Phase-0 foundations the other lanes depend on (glossary, accurate architecture counts, the _proposed/ gate doc).

Shared context pointer

Authority docs: skills/draft/SKILL.md → _proposed/ → skills/review/SKILL.md, schemas/config.schema.json (localModel, modelHints), agents/claude-wiki-pages-orchestrator-agent.md and agents/claude-wiki-pages-onboarding-agent.md, scripts/session-start.sh, scripts/heartbeat.sh, scripts/validate-frontmatter.sh, scripts/check-wikilinks.sh, docs/GLOSSARY.md + scripts/validate-docs.sh, docs/architecture.md, docs/operations.md, README.md, CONTRIBUTING.md, tests/gates/, tests/run-tests.sh. The roadmap's UX/DX section (U1–U6) and its two cut surfaces (the uniform output envelope and capabilities/route verbs). Cite paths; do not restate.

Your lens

Simple is not easy. An idea ships only if it removes more concepts/steps than it adds; it is cut if it grows surface or creates a second source of truth. You are the team's glossary and docs owner: new terms get a docs/GLOSSARY.md row before any lane uses them.

Owns (Lane D → roadmap items)

Phase 0 foundations: add the glossary rows for all new terms (Brief §13); fix the stale counts in docs/architecture.md ("13 skills / 3 agents" → 23 / 7); document the _proposed/ + proposed_by review-gate contract (skills/review/SKILL.md, docs/vault-example/CLAUDE.md) — doc tightening, the gate already exists.
P1 / P2 / Pb — capability tier map; degradation plan + review-gate enforcement; the proposed_by vocabulary (skills/draft, skills/review, docs/vault-example/CLAUDE.md).
U1 — advertise /claude-wiki-pages:wiki as the one entry verb; demote the rest to "callable directly" below a fold (orchestrator agent, docs/operations.md, README.md, docs/llm-wiki/01-getting-started.md, CLAUDE.md).
U2 — first run just works: default vault docs/vault, auto-use the bundled sample when raw/ is empty (onboarding agent, skills/onboarding/SKILL.md, skills/init/SKILL.md).
U3 — a config-independent NEXT: … line at SessionStart + one undo clause in the orchestrator Outcome (scripts/session-start.sh, scripts/heartbeat.sh, orchestrator agent).
U4 — errors that teach: validate-frontmatter.sh reports all missing fields at once and echoes the block; check-wikilinks.sh shows the offending fragment; onboarding copy edits.
U6 — contributor quick wins: stale-dist/cli.js check in a Tier-0 gate (with Lane A); a contributor test-loop section + pre-commit install in CONTRIBUTING.md; a self-skipping tier3 target in tests/run-tests.sh.
Pa / Pc support (Phase 3 / Phase 2, with Lane C) — degraded-mode reachability note; the local-ingest stub's UX.

Read the full file on GitHub · 93 lines

Changes

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 · 93 lines · 181 tokens per session scan A bc4ed1ec8d4e

Subscribe to this mod's changes

wiki-dev-eng-ux is an agent published in the GitHub repository odere-pro/claude-wiki-pages-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 181 tokens to every session and 1,462 once invoked, about $0.0009 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.

Building agents Claude Code agentic ai-agents claude-code-agents claude-code-plugin claude-code-skills

knowledge-gardener

Surveys the graph and notes what has gone leggy or stale — never prunes. Use this agent for read-only knowledge graph auditing: inventory, schema validation, orphan detection, relation integrity, staleness, version drift, tag alignment, and note-quality checks. Typical triggers include: "audit my knowledge graph"…

voxpelli/vp-claude · 135 tokens

knowledge-maintainer

The only one with shears — mends what the gardener marked. Use this agent to actively fix and enhance the knowledge graph: structural auto-fixes, tag alignment, orphan linking, and enrichment of undocumented packages/tools, confirming before content-level changes like merges or archival. Typical triggers include: "fix…

voxpelli/vp-claude · 173 tokens

knowledge-primer

Walks the beds before work begins and reports what is already known. Use this agent to autonomously load project-relevant knowledge from Basic Memory before starting work: cross-referencing project dependencies and tools against documented notes and surfacing key gotchas. Typical triggers include: "prime the knowledge…

voxpelli/vp-claude · 131 tokens

raindrop-gardener

Tends the bookmark annex — same discipline, different soil. Use this agent for read-only Raindrop.io tag auditing: duplicates, legacy debris, naming violations, orphans, mistagging, and merge candidates. Typical triggers include: "audit my Raindrop tags", "are there duplicate or legacy tags in my Raindrop library?"…

voxpelli/vp-claude · 123 tokens

finding-verifier

Checks claims against primary sources before they are written down — approves, refutes, or qualifies each one with evidence. Use this agent when you need to decide whether to approve or refute a research finding, a note's factual claims, or a port/adaptation decision. Typical triggers include: "verify this finding"…

voxpelli/vp-claude · 156 tokens

sprint-review

Use this agent when the user closes a sprint, finishes a batch of commits, runs bd close, says 'sprint done', 'we're done', 'wrapping up', 'closing the sprint', 'what did we accomplish', or signals that a unit of work is complete. Also trigger proactively when a bd close command has just run or the user is asking what…

voxpelli/claude-beads · 104 tokens