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/itechmeat/llm-code/seaweedfsnpx skills add itechmeat/llm-code --skill seaweedfsgit clone --depth 1 https://github.com/itechmeat/llm-codeWhat 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.00065 | $0.02709 |
| Opus 5 | $0.00032 | $0.01354 |
| Sonnet 5 | $0.00013 | $0.00542 |
| Haiku 4.5 | $0.00006 | $0.00271 |
Grade A, and why
seaweedfs 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SeaweedFS
This skill is a practical router for deploying and operating SeaweedFS from the upstream repository and wiki.
Prefer production guidance from multi-component setups over weed mini shortcuts.
Quick Navigation
| Situation | Open |
|---|---|
| Learn the system shape and bootstrap paths | references/getting-started.md |
| Stand up a local all-in-one sandbox | references/quick-start-mini.md |
| Review control-plane, volume, and collection topology | references/topology-and-setup.md |
| Check master, volume, filer, and client API surfaces | references/api-surfaces.md |
| Set replication, TTL, failover masters, and env vars | references/configuration.md |
| Work with performance notes, FAQ topics, and examples | references/benchmarks-and-use-cases.md |
| Work with filer metadata, uploads, JWT, and TUS | references/filer-core.md |
| Choose and scale filer metadata stores | references/filer-stores.md |
| Operate S3 buckets, auth, and IAM/OIDC | references/s3-gateway.md |
| Plan Cloud Drive and remote storage mounts | references/cloud-drive.md |
| Run backups, metrics, repairs, and shell workflows | references/backup-and-replication.md, references/operations.md |
| Choose S3 encryption and client tooling | references/encryption.md, references/s3-client-tools.md |
| Review transport, JWT, TLS, and exposure controls | references/security.md |
What ships with it
18 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- plan.md 4.8 KB
- references/api-surfaces.md 11 KB
- references/backup-and-replication.md 4.5 KB
- references/benchmarks-and-use-cases.md 6.7 KB
- references/cloud-drive.md 5.7 KB
- references/configuration.md 12 KB
- references/encryption.md 2.7 KB
- references/filer-core.md 14 KB
- references/filer-stores.md 10 KB
- references/getting-started.md 2.7 KB
- references/operations.md 5.9 KB
- references/quick-start-mini.md 3.1 KB
- references/s3-api.md 174 B
- references/s3-auth-iam.md 208 B
- references/s3-client-tools.md 3.3 KB
- references/s3-gateway.md 9.1 KB
- references/security.md 4.3 KB
- references/topology-and-setup.md 7.2 KB
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 · 122 lines · 65 tokens per session scan A 608f1a84c2a2
seaweedfs is a skill published in the GitHub repository itechmeat/llm-code (22 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 2,709 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-30.
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…