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 glitchwerks/claude-wayfinder --skill dispatch-authoringgit clone --depth 1 https://github.com/glitchwerks/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/dispatch-authoring)<a href="https://agentmods.dev/skills/glitchwerks/claude-wayfinder/dispatch-authoring"><img src="https://agentmods.dev/badge/skills/glitchwerks/claude-wayfinder/dispatch-authoring/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/dispatch-authoring"><img src="https://agentmods.dev/badge/skills/glitchwerks/claude-wayfinder/dispatch-authoring.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.00222 | $0.07993 |
| Opus 5 | $0.00111 | $0.03997 |
| Sonnet 5 | $0.00044 | $0.01599 |
| Haiku 4.5 | $0.00022 | $0.00799 |
Grade A, and why
dispatch-authoring 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 10d 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 — 609 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontmatter Authoring Guide
This skill covers everything you need to write, improve, and troubleshoot trigger frontmatter for claude-wayfinder agents and skills. It explains what fields the matcher reads, how scoring works, the seven routing decisions the matcher can produce, and the most common mistakes that cause an entry to match poorly or never match at all.
1. What the Matcher Consumes
Source precedence
The catalog generator accepts trigger configuration from two places: inline frontmatter inside the agent or skill file itself, and a sidecar file placed next to the main file. The sidecar always wins when both are present.
The current sidecar format is v6. Under v6:
-
A skill stores its trigger configuration in a file named
triggers.ymlplaced in the same directory asSKILL.md:skills/python/SKILL.md skills/python/triggers.yml ← authoritative trigger configPer issue #150, a colocated
<name>.triggers.ymlnext toSKILL.md(owned and project agent sidecars) overrides inline frontmatter. TheSKILL.mdfile itself should not containtriggers:,applicable_agents:, orapplicable_skills:keys; the generator emits a warning and ignores them if they appear there. -
A plugin-shipped agent stores its trigger override at
triggers/<plugin>/agents/<name>.yml(per issue #142). This file activates a dormant plugin agent that would otherwise score zero.
For the canonical field reference see docs/schema.md. For the design
discussion behind the sidecar approach see docs/design/trigger-schema.md.
Schema fields
| Field | Where it lives | Purpose |
|---|---|---|
command_prefixes |
triggers: block |
Slash commands that immediately short-circuit to score 1.0. |
agent_mentions |
triggers: block |
Agent names whose explicit mention in the prompt immediately short-circuits to score 1.0. |
path_globs |
triggers: block |
fnmatch-style globs matched against the file_paths dimension of the input. Each matched glob adds 0.4 to the score. |
keywords |
triggers: block |
List of {term, weight} mappings. Each term found in the input keywords adds 0.5 × weight to the score. Terms are Porter2-stemmed unless no_stem: true is set (see § 1 "Stemming"). |
no_stem |
per-keyword flag | Optional no_stem: true on a {term, weight} mapping exempts that term from stemming — it matches the raw (unstemmed) input token verbatim. Use for acronyms, product names, and CLI flags (aws, gh, ps1). |
keyword_groups |
triggers: block |
AND-group conjunctive triggers (added v0.6.0, #135). List of {slots: [{name, terms: [...]}, ...], weight} groups. A group fires only when all of its slots match — each slot must have ≥ 1 of its terms present in the input keywords. On match, the group adds 1.0 × weight (via _GROUP_MULTIPLIER, distinct from the 0.5 _KEYWORD_MULTIPLIER so a satisfied weight-1.0 group can solo-decide delegate). Use when a routing decision should require co-occurrence of two or more terms (e.g. verb + noun) rather than either alone. |
tool_mentions |
triggers: block |
Tool names matched against the input tool_mentions dimension. Each match adds 0.5. |
excludes |
triggers: block |
Terms that hard-zero the entry's score when found in the input keywords. |
applicable_agents |
skill sidecar top-level | Hard allowlist of agent names that may receive this skill. ["*"] means any agent. [] means no agent — the skill is dormant. |
applicable_skills |
agent sidecar top-level | Hard allowlist of skill names to attach when routing to this agent. ["*"] means any. [] means no skills. |
routable |
agent frontmatter top-level | When false, the agent is excluded from the scored-agent pool. Set to false on the router itself so it is never selected as a delegation target. Absent on skill entries. |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 609 lines · 222 tokens per session scan A 6ef448c88a1a
dispatch-authoring is a skill published in the GitHub repository glitchwerks/claude-wayfinder (2 stars, last pushed today), licensed MIT. It adds 222 tokens to every session and 7,993 once invoked, about $0.0011 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
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…
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…
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.…
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…
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.
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.