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/shift-notesnpx skills add agentdecksdk/agentdeck --skill shift-notesgit 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.00024 | $0.00125 |
| Opus 5 | $0.00012 | $0.00063 |
| Sonnet 5 | $0.00005 | $0.00025 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
shift-notes 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 yesterday.
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.
What it actually says
A handover note has three parts, in this order: what changed during the shift, what is still open, and what the next shift should watch for.
Keep it to three sentences, one per part. If the user has not said what is still open, ask before filing - a note that invents an open item is worse than no note.
File it against the date the shift ran, not the date it was written, if those differ.
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.
- yesterday First seen · 13 lines · 24 tokens per session scan A 6a56e33cc1b1
shift-notes is a skill published in the GitHub repository agentdecksdk/agentdeck (2 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 125 once invoked, about $0.0001 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.