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/seenode/seenode-agent-plugin/storagenpx skills add seenode/seenode-agent-plugin --skill storagegit clone --depth 1 https://github.com/seenode/seenode-agent-pluginWhat 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.00053 | $0.00533 |
| Opus 5 | $0.00026 | $0.00267 |
| Sonnet 5 | $0.00011 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
storage 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Application storage on Seenode
Persistent volumes attach to a single application. Apps may have at most one active volume. Scale must be 1 when storage is attached.
Discover packages and volumes
list_storage_packages()
list_application_storage(application_id=...)
Use package sizes (GiB) when creating or resizing. Confirm the app’s scale via get_application before attaching storage.
Create / attach
create_application_storage(
application_id=...,
mount_path="/data", # absolute path required
size=null, # GiB from list_storage_packages; default 5
custom_name=null
)
Side effect: provisions asynchronously. Confirm with the user before paid size tiers; check get_credit_balance when spend is a concern. Quote package pricePerMonthUsd / creditBalanceUsd only (never DIY cents→dollars).
Update (resize / remount / rename)
update_application_storage(
application_id=...,
storage_uuid=...,
mount_path=null,
size=null, # can only increase — never shrink
custom_name=null
)
Resizing is asynchronous — status becomes RESIZING until complete. Resolve storage_uuid from list_application_storage.
Metrics
get_application_storage_metrics(
application_id=...,
storage_uuid=...,
range_hours=24
)
Use for capacity pressure while troubleshooting disk-full symptoms.
Safety
- No delete-storage tool via MCP — remove volumes in the dashboard.
- Do not attach storage when scale > 1; do not claim shrink/downgrade is possible.
- Inspect before mutate; preserve MCP approval prompts.
Relevant tools
list_storage_packages, list_application_storage, create_application_storage, update_application_storage, get_application_storage_metrics, get_application, get_credit_balance
Related skills
- applications — scale and package constraints
- deploy — optional volume during first ship
- troubleshoot — disk/capacity symptoms
- billing — credit before paid sizes
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 · 79 lines · 53 tokens per session scan A 5d599cc97f01
storage is a skill published in the GitHub repository seenode/seenode-agent-plugin (2 stars, last pushed 23d ago), licensed MIT. It adds 53 tokens to every session and 533 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…