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/vaayne/agent-kit/openlistnpx skills add vaayne/agent-kit --skill openlistgit clone --depth 1 https://github.com/vaayne/agent-kitWhat 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.00103 | $0.00811 |
| Opus 5 | $0.00051 | $0.00405 |
| Sonnet 5 | $0.00021 | $0.00162 |
| Haiku 4.5 | $0.00010 | $0.00081 |
Grade A, and why
openlist 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenList File Manager
Manage files on an OpenList server via its REST API. OpenList is an AList-compatible multi-storage file listing program.
Setup
{project} is the git repo name (if in a git repo) or the basename of the current working directory.
Copy both SDK and CLI to ~/.agents/sessions/{project}/scripts/, then load env vars:
cp skills/openlist/scripts/openlist_client.py skills/openlist/scripts/openlist.py ~/.agents/sessions/{project}/scripts/
source ~/.zshenv
Environment variables
| Variable | Required | Notes |
|---|---|---|
OPENLIST_URL |
Yes | Base URL e.g. http://localhost:5244 |
OPENLIST_TOKEN |
One of these | Pre-issued JWT token (preferred) |
OPENLIST_USERNAME |
One of these | Username for login |
OPENLIST_PASSWORD |
If USERNAME set | Password for login |
Workflow
- Verify env vars are set (
OPENLIST_URL+ auth). - Clarify the target path(s), operation, and any dry-run requirement.
- Pick the right approach:
| Scenario | Approach |
|---|---|
| Single operation (ls, rename, mv, mkdir, rm, regex-rename) | Bundled CLI directly |
| Multi-step workflow (mkdir → move → rename → cleanup) | Task script importing SDK |
| Needs dry-run preview of a complex plan | Task script |
| Needs retry logic (e.g. Quark async moves) | Task script |
- For task scripts: lint with
uvx ruff check --fix, run withuv run --script. - Report results.
Bundled CLI & SDK
scripts/openlist_client.py—OpenListClientclass +size_fmthelper. Import in custom scripts:import sys from pathlib import Path sys.path.insert(0, str(Path(__file__).parent)) from openlist_client import OpenListClientscripts/openlist.py— CLI wrapper covering all endpoints. Run as:SCRIPT="uv run --script ~/.agents/sessions/{project}/scripts/openlist.py" $SCRIPT ls "/quark/来自:分享/TVs" $SCRIPT rename "/path/to/old" "new-name"
What ships with it
5 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.
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 · 79 lines · 103 tokens per session scan A 893855428f7f
openlist is a skill published in the GitHub repository vaayne/agent-kit (53 stars, last pushed 5d ago), licensed MIT. It adds 103 tokens to every session and 811 once invoked, about $0.0005 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…