agentmods.dev

wiki_ticket_sdd: Skill for Claude Code

.claude/skills/wiki-publish/SKILL.md

wiki-publish is a skill for Claude Code from SpillwaveSolutions/wiki_ticket_sdd. It costs 54 tokens per session (2,147 once invoked), scanned A, original, MIT.

A skill for publishing repository documents to a team wiki, such as roadmaps, plans, guides, and status reports. A wiki is a shared website for team documentation.

In plain words
What is it for?
Use it to sync selected documents to the configured wiki after checking the repository's publication manifest and document safeguards.
Why use it?
It determines which pages need publishing and avoids overwriting unchanged or protected documents. It also records what was published.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is SpillwaveSolutions/wiki_ticket_sdd's own configuration. It tells Claude Code how to work on wiki_ticket_sdd itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything wiki_ticket_sdd configures →

not rated 10repo changed 5d ago A scan 54 tokens original MIT
View source ↗ SpillwaveSolutions/wiki_ticket_sdd
Reuse

Borrowing it

Nothing to install: this file belongs to SpillwaveSolutions/wiki_ticket_sdd. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/SpillwaveSolutions/wiki_ticket_sdd/main/.claude/skills/wiki-publish/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/SpillwaveSolutions/wiki_ticket_sdd

Made for: Claude Code.

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.

agentmods badge for wiki-publish

README.md
[![agentmods](https://agentmods.dev/badge/skills/spillwavesolutions/wiki_ticket_sdd/wiki-publish/github.svg)](https://agentmods.dev/skills/spillwavesolutions/wiki_ticket_sdd/wiki-publish)
Your own site
<a href="https://agentmods.dev/skills/spillwavesolutions/wiki_ticket_sdd/wiki-publish"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/wiki_ticket_sdd/wiki-publish/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.

agentmods 80×15 button for wiki-publish

Your own site · 80×15
<a href="https://agentmods.dev/skills/spillwavesolutions/wiki_ticket_sdd/wiki-publish"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/wiki_ticket_sdd/wiki-publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,147 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.02147
Opus 5 $0.00027 $0.01073
Sonnet 5 $0.00011 $0.00429
Haiku 4.5 $0.00005 $0.00215

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

Security

Grade A, and why

wiki-publish 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 5d 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/skills/wiki-publish/SKILL.md · 181 lines

How it starts

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

Wiki publish

No per-system code ships with this skill. The dispatcher (worklog wiki-plan) owns skip and the frozen guard. This skill's job is to run it, push the pages it names, and wiki-record the result — not to re-implement the rules.

0. Dispatcher owns skip and the frozen guard

  1. If docs/.index/publish-manifest.json is missing or stale, run worklog ia-index (worklog ia-render --check tells you).
  2. bin/worklog wiki-plan — reads the manifest and the folded ledger. Prints JSON {publish, skip, frozen_violations}.
  3. If the command exits 1, frozen_violations is a frozen-doc source edit (body hash drifted). Stop and report. Do not publish.
  4. Publish only the pages in publish. skip is already on the wiki (render_hash match). A frozen page whose banner moved has a new render_hash and a matching source_hash — those are in publish.
  5. Copy source_hash and render_hash from the plan entry into worklog wiki-record. Never hash files yourself.

For each page in publish:

  • render: "as-is" — publish the file (frontmatter-strip of §3 still applies).
  • render: "doc+banner" — strip per §3, then prepend the page's banner line plus a blank line. Banners are publish-time renders; never write them into docs/ sources.
  • page_name _Sidebar publishes as _Sidebar.md.

Never publish docs/.index/ internals: only manifest-listed sources reach the wiki. The JSON/YAML files (inventory, graph, manifest, aliases, sidecars) are internal join data.

1. Read the config

Read the wiki: block in .work/config.yml. system names the wiki: github-wiki, gitlab-wiki, ado-wiki, confluence, other, or none. If it is none or absent, say so and stop — there is nothing to publish to. The enum is advisory — other is any wiki not listed (Notion, MediaWiki, a docs site): set it, name the real system in options:, and resolve the tooling at runtime like any other system below.

2. Pick the tooling

Read the full file on GitHub · 181 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.

  1. 5d ago Changed 8b7823dd590b
  2. 9d ago First seen · 181 lines · 54 tokens per session scan A 6bbfe1497d1a

Subscribe to this mod's changes

wiki-publish is a skill published in the GitHub repository SpillwaveSolutions/wiki_ticket_sdd (10 stars, last pushed 7d ago), licensed MIT. It adds 54 tokens to every session and 2,147 once invoked, about $0.0003 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.

Writing and docs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens