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/agentdecksdk/agentdeck/ship-issuenpx skills add agentdecksdk/agentdeck --skill ship-issuegit clone --depth 1 https://github.com/agentdecksdk/agentdeckWhat 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.00041 | $0.01086 |
| Opus 5 | $0.00020 | $0.00543 |
| Sonnet 5 | $0.00008 | $0.00217 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
ship-issue 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 2d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship an issue
Orchestrate the end-to-end delivery of an issue.
0. Brief Before Launching
Read the issue and verify its claims against the tree. Spec gate first: if the issue lacks Done when outcomes or scope bounds (what must NOT be added), fix the issue body or ask the user; do not spawn deck-dev against an unbounded spec. Then output a concise 5-point brief (1–2 lines each):
The claim: What the issue asks for. What's true now: Current behavior in the codebase (file:line). The shape: Implementation plan in 3–4 concise bullets. The hard gate: Invariants that must not break (
tests/golden/, public API, import law). Skipped: What is deliberately out of scope.
1. Board Tracking
Update GitHub Project (PVT_kwHOBHijkM4BgHFZ): Set Status = In progress, record Start Date, comment with start timestamp.
2. Implement
Spawn deck-dev with the issue number and brief. It runs Stage 0 (Understand) then Stage 1
(Design, posted to the draft PR body), then stops there and reports back rather than continuing
into Stage 2.
If it stops at its own spec gate despite step 0, the issue needs a human decision: set the board back to Todo, surface what is missing, stop the pipeline.
Design gate: compare the reported design against this step's own brief. A design is never
blocked for being larger; it is blocked only for a named problem: a duplication of something
already in scripts/repomap.py's output, an abstraction with one caller, a divergence from its
own declared ## Analog, configuration for a value that never changes. No such problem: send
deck-dev a message to proceed to Stage 2. A problem found: send it back naming the problem, not
a target size; deck-dev revises Stage 1 and reports again before Stage 2 starts.
Once past the gate, deck-dev continues through Implement, Self-review, and Gate, posting task
progress; poll for stalls.
3. Attach PR
Verify the draft PR targets dev, includes Closes #<n>, and its body carries the design sections (## Reuse analysis, ## Analog, ## Concept budget, ## Expected delta). Missing sections go back to deck-dev before any review is spent. Set Status = In review when marked ready.
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.
- 2d ago First seen · 68 lines · 41 tokens per session scan A 60ef4e02cd36
ship-issue is a skill published in the GitHub repository agentdecksdk/agentdeck (2 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 1,086 once invoked, about $0.0002 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
png-press
Teaches agents how to author content and configure writepng so PNGs render at the correct size, with tight cropping, readable text, and consistent scaling.
bundle-builder
Build or repair KDCube bundles. Use the KDCube bundle docs, the workspace reference bundle, and the shared bundle suite before writing code.
sources-section
Appends a Sources/References section using only web sources from the sources pool.
local-runtime
Start local KDCube, reload one bundle, stop the local runtime, or run the shared bundle suite.
bootstrap-local
Generate a clean local descriptor set for one KDCube bundle and print the exact next commands to start it.
automations
Create, inspect, edit, archive, delete, run, and search scheduled or executable automation assets.