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 agentmods add skills/spillwavesolutions/wiki_ticket_sdd/ticket-syncnpx skills add SpillwaveSolutions/wiki_ticket_sdd --skill ticket-syncgit clone --depth 1 https://github.com/SpillwaveSolutions/wiki_ticket_sddWrote 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/spillwavesolutions/wiki_ticket_sdd/ticket-sync)<a href="https://agentmods.dev/skills/spillwavesolutions/wiki_ticket_sdd/ticket-sync"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/wiki_ticket_sdd/ticket-sync.svg" alt="Measured on agentmods" 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 | $0.00056 | $0.01713 |
| Opus 5 | $0.00028 | $0.00856 |
| Sonnet 5 | $0.00011 | $0.00343 |
| Haiku 4.5 | $0.00006 | $0.00171 |
Grade A, and why
ticket-sync 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 today.
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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticket sync
Sync runs through a typed adapter contract: the dispatcher
(bin/sync_dispatch.py) owns every invariant; a per-system adapter is a
dumb translator. This skill's job is to run it and read the report — not
to re-implement the rules. Contract:
docs/plans/2026-07-18-typed-adapter-contract.md.
1. Read the config
Read the ticketing: block in .work/config.yml. system names the
tracker: github, gitlab, jira, ado, linear, codecatalyst,
other, or none. If it is none or absent, say so and stop — there is
nothing to push to.
The enum is advisory, not a capability list. bin/worklog only ever
branches on none; every other value is a name this skill resolves to
whatever tooling exists (CLI, MCP server, REST). Named values carry known
caveats; other is any tracker not listed — set it, note the real system
in options:, and the skill researches the tooling at runtime.
- linear — no git remote to detect; reach it via the Linear MCP server or CLI. Markers go in the issue description (markdown survives).
- codecatalyst — AWS's ADO equivalent (issues per project). Closed to
NEW customers since 2025-11-07; existing spaces keep working. Reach via
aws codecatalystCLI. - GCP has no native work tracker — GCP-hosted teams pick one of the
above (or
other); there is nogcpvalue to configure.
2. Scope
Open items plus externally-linked items whose canonical hash differs from the last pushed one; closed and in-sync items are inert (spec §10.5 — the dispatcher computes this, see the contract doc).
3. Flow
bin/worklog adapter check— activates and validates the adapter for the configured system against the contract. Missing adapter → the dispatcher runs local-only; that is a mode, not an error.bin/worklog sync— the dispatcher handles scope, hash-skip, create-vs-update, echo suppression, conflict detection, andworklog ingestof pulled changes.- Read the drift report and surface anything that needs a human (conflicts, unsupported fields, degraded type mappings, auth failures, unmarked remotes, closed-on-remote items).
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.
- today Changed 437a56f6b28f
- 4d ago First seen · 144 lines · 56 tokens per session scan A 8d0fc6ae3c20
ticket-sync is a skill published in the GitHub repository SpillwaveSolutions/wiki_ticket_sdd (10 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 1,713 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.
Other skills, from other repositories
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.