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/issue-descriptionnpx skills add SpillwaveSolutions/wiki_ticket_sdd --skill issue-descriptiongit 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/issue-description)<a href="https://agentmods.dev/skills/spillwavesolutions/wiki_ticket_sdd/issue-description"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/wiki_ticket_sdd/issue-description.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.00050 | $0.00581 |
| Opus 5 | $0.00025 | $0.00291 |
| Sonnet 5 | $0.00010 | $0.00116 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
issue-description 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rich issue descriptions
An issue is a durable intent record, not a task title. Issues outlive PRs and are read by more people — including future agents. Every issue should let a zero-context reader understand what, why, where it sits, and what "done" looks like.
The mechanical path (worklog-synced tickets)
For items in the event log, do not hand-write bodies:
bin/worklog ticket-body <ulid> renders the item's graph node — summary
(from --body), context (epic, generating plan with its frozen wiki page,
milestone, unplanned provenance), and traceability (decides/implements
edges, delivered-by PRs). ticket-sync pushes that. To make a ticket richer,
enrich the SOURCE: worklog update --body, worklog link-pr, sidecar
relates_to edges — never just the remote ticket (it would drift back).
Template (hand-written issues, or systems without worklog)
## Summary
One or two sentences: what needs to be done and why it matters.
## Context / Big picture
Where this sits in the larger system or epic. Link the parent epic and
the plan that generated it.
## Problem / Motivation
What is painful or missing today? "What"-only issues rot; "why" keeps
them useful.
## Desired outcome
What does done look like? Concrete and observable.
## Scope
In scope: ...
Explicitly out of scope: ...
## Proposed approach (optional)
High-level design or sequence if known. Link relevant ADRs/design docs.
## Acceptance criteria
- [ ] ...
## Traceability
Plan / Epic / ADRs / Spec sections / Related issues.
## Notes for implementers & agents
Traps, sequencing rules, non-obvious constraints, "never do X" guidance
written for the next agent that picks this up.
Rules
- Omit sections that have no real content — no boilerplate placeholders.
- Every plan-generated issue links back to its frozen plan page: the why lives in the plan, the issue carries the pointer.
- Surface risks and open questions early; uncertainty stated is uncertainty managed.
- Body text must be readable by a junior dev or PM: no bare ULIDs in prose (spec §13.4); ULIDs belong in the machine footer.
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 4930798796a2
- 4d ago First seen · 67 lines · 50 tokens per session scan A 2f9ad7893de6
issue-description is a skill published in the GitHub repository SpillwaveSolutions/wiki_ticket_sdd (10 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 581 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.