Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add glitchwerks/claude-wayfinder/plugin install claude-wayfinderWrote 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/glitchwerks/claude-wayfinder/setup-wayfinder)<a href="https://agentmods.dev/skills/glitchwerks/claude-wayfinder/setup-wayfinder"><img src="https://agentmods.dev/badge/skills/glitchwerks/claude-wayfinder/setup-wayfinder/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/glitchwerks/claude-wayfinder/setup-wayfinder"><img src="https://agentmods.dev/badge/skills/glitchwerks/claude-wayfinder/setup-wayfinder.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.00122 | $0.02509 |
| Opus 5 | $0.00061 | $0.01255 |
| Sonnet 5 | $0.00024 | $0.00502 |
| Haiku 4.5 | $0.00012 | $0.00251 |
Grade D, and why
setup-wayfinder scanned grade D with 2 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 11d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Offer the common-cause hint: on Debian/Ubuntu, `sudo apt install python3-venv` is often needed. Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$PLUGIN_DATA/venv" How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup claude-wayfinder
Materialize the Python venv at ${CLAUDE_PLUGIN_DATA}/venv/ so plugin hooks can spawn a Python that has claude_wayfinder importable. Write the setup-state flag so hooks know setup completed.
The behavior described below is mirrored by tests/integration/setup_pipeline.py. If you change anything here, update that file too (CI's test_skill_pipeline_sync.py enforces this).
Step 1: Resolve ${CLAUDE_PLUGIN_DATA}
The plugin data directory path is keyed <plugin>-<marketplace> by the harness, and the same plugin resolves under different marketplace keys across surfaces — claude-wayfinder-glitchwerks on a CLI surface, claude-wayfinder-inline on a desktop/ccd surface. Two sources are available, in priority order:
- Runtime env var
$CLAUDE_PLUGIN_DATA(no braces) — the test seam, but the harness sets it to whichever plugin invoked the current surface, so another plugin's data dir can leak in (e.g.codex-inline). Honor it only when its basename is a same-plugin key:claude-wayfinder-<marketplace>with exactly one marketplace segment after the plugin name (-glitchwerks,-inline, …). This admits every marketplace variant while rejecting two leak classes — unrelated plugins (codex-inline) and prefix-colliding sibling plugins whose own name starts withclaude-wayfinder-(e.g.claude-wayfinder-helper→ keyclaude-wayfinder-helper-inline, which has a second-segment). Do not require an exact-glitchwerksmatch — that is the bug this guard replaces (it rejected the legitimate-inlinedesktop key and silently misinstalled into the CLI-keyed dir, leaving every desktop session stuck on the "requires setup" banner). Do not loosen it to a bareclaude-wayfinder-*prefix either — that re-admits the sibling-plugin collision. - Harness-rendered literal
${CLAUDE_PLUGIN_DATA}(braces) — the harness substitutes this token in the skill body at load time with this session's correct data dir. Prefer it over a hardcoded-glitchwerksslug whenever the runtime env var is unusable (cross-plugin leak, or unset). - Computed slug (
claude-wayfinder-glitchwerks) — last resort only, for raw execution outside the harness where neither source above is available.
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.
- 11d ago First seen · 203 lines · 122 tokens per session scan D 5a9878aa596d
setup-wayfinder is a skill published in the GitHub repository glitchwerks/claude-wayfinder (2 stars, last pushed today), licensed MIT. It adds 122 tokens to every session and 2,509 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
analytics-strategy
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…
content-strategy
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…
incident-response
Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
agb-begriff-vorformuliert-305
Für AGB Begriff Vorformuliert 305: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-begriff-vorformuliert-305.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.