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 skills add ashtonian/llm-init --skill shelvegit clone --depth 1 https://github.com/ashtonian/llm-initWrote 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/ashtonian/llm-init/shelve)<a href="https://agentmods.dev/skills/ashtonian/llm-init/shelve"><img src="https://agentmods.dev/badge/skills/ashtonian/llm-init/shelve.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.1 | $0.00011 | $0.00360 |
| Opus 5 | $0.00005 | $0.00180 |
| Sonnet 5 | $0.00002 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
shelve 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 8d 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.
What it actually says
Checkpoint current work with a structured handoff state.
Instructions
- Assess current work state:
- What task or plan is currently in progress?
- What files have been modified? (
git diff --name-only) - What's the current git branch?
- Record the current Claude Code session ID for potential
--resumeon pickup. - Create a structured handoff state with these sections:
- Completed Steps -- what's done
- Current Step -- what was in progress
- Files Modified -- list of changed files
- Key Decisions -- design choices made during this session
- Known Issues -- problems the next agent should know about
- Next Actions -- where to pick up
- Session ID -- current session ID (for
--resume)
- If working on a task file (in
docs/spec/.llm/tasks/):- Write the handoff state to the task's
## Handoff Statesection - Commit WIP changes on the task branch
- Move the task back to
docs/spec/.llm/tasks/backlog/
- Write the handoff state to the task's
- If working on a plan file (in
docs/spec/.llm/plans/):- Update the plan's Progress Log with the handoff state
- Commit WIP changes
- Update
docs/spec/.llm/PROGRESS.mdwith any learnings from this session. - Confirm the shelve to the user with a summary of what was saved.
$ARGUMENTS
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.
- 8d ago First seen · 35 lines · 11 tokens per session scan A d77a0ee64254
shelve is a skill published in the GitHub repository ashtonian/llm-init (2 stars, last pushed 7mo ago), licensed MIT. It adds 11 tokens to every session and 360 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.