What is wiki_ticket_sdd CLAUDE.md?

A set of rules for managing software work in the Acme platform. Work items are recorded in a project file, while plans act as the lasting explanation of what will be built and why.

It helps break requests into tracked tasks, record implementation plans, update task progress, and publish plans as tickets and wiki pages.

It prevents work and planning decisions from being lost or made outside the project's tracking system.

How SpillwaveSolutions/wiki_ticket_sdd configures Claude Code

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

README.md

[![agentmods](https://agentmods.dev/badge/instructions/spillwavesolutions/wiki_ticket_sdd/claude-md/github.svg)](https://agentmods.dev/instructions/spillwavesolutions/wiki_ticket_sdd/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/spillwavesolutions/wiki_ticket_sdd/claude-md"><img src="https://agentmods.dev/badge/instructions/spillwavesolutions/wiki_ticket_sdd/claude-md/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/instructions/spillwavesolutions/wiki_ticket_sdd/claude-md"><img src="https://agentmods.dev/badge/instructions/spillwavesolutions/wiki_ticket_sdd/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,502 This file is loaded in full into every session.

When invoked 1,502 The same file — it is already loaded in full.

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.01502	$0.01502
Opus 5.5	$0.00601	$0.00601
Sonnet 5.5	$0.00300	$0.00300
Haiku 4.5	$0.00150	$0.00150

Measured 2mo ago against content hash 9d884c8a5169, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

wiki_ticket_sdd CLAUDE.md 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 2mo 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.md · 106 lines

How it starts

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

Acme Platform

Work tracking policy

Work items live in .work/todo.jsonl. Settings live in .work/config.yml — read that file; do not infer settings from this document. This file is policy only, which is why AGENTS.md is a symlink to it: one policy, every harness. Do not add harness-specific notes here.

Every request that produces work is broken into worklog items FIRST. Run bin/worklog add (see the work-track skill) before starting, and move items in_progress → done as the work happens — the UserPromptSubmit and Stop hooks enforce this. Unrecorded work is invisible work.
Exiting plan mode is not optional bookkeeping. Every plan MUST end by running worklog plan-capture, which writes docs/plans/<date>-<name>.md and appends the plan's steps as work items. This is also enforced by a hook; if you find yourself ending a plan without it, that's a bug, not a shortcut. After capture, plans and their items are published (tickets + wiki) by a background subagent; implementation never waits on publishing.
Plans are the permanent design record. docs/plans/ is where the why lives — it is the specification half of spec-driven development, checked into the repo and published to the wiki for exactly that reason. A plan is written once and never regenerated or rewritten. If the design changed, write a NEW plan with supersedes: <slug> in its front matter. Do not edit history: the record of why the first approach was abandoned is the most valuable thing in the file. When you need to know why a decision was made, read the plan, not the ticket.
If you discover work mid-flight that wasn't in the plan — a bug, a missing migration, a broken test — run worklog add --unplanned --discovered-during <item> BEFORE doing the work. Do not silently absorb it. Unplanned work that never gets recorded is why estimates never improve.
When a plan is complete, run worklog sync. This closes items, updates the ticketing system, regenerates the roadmap, and publishes. Partial failure is expected and fine — sync is best-effort by design and reports its drift.

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

2mo ago First seen · 106 lines · 1,502 tokens per session scan A 9d884c8a5169

Subscribe to this mod's changes

wiki_ticket_sdd CLAUDE.md is an instructions file published in the GitHub repository SpillwaveSolutions/wiki_ticket_sdd (11 stars, last pushed 1mo ago), licensed MIT. It adds 1,502 tokens to every session, about $0.0060 per session on Opus 5.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.

Project management

wiki_ticket_sdd CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
wiki_ticket_sdd CLAUDE.mdSpillwaveSolutions/wiki_ticket_sdd	Instructions file	11	1mo ago	MIT	A	1,502	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

wiki_ticket_sdd: Instructions file for Claude Code