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/toss/es-toolkit/guidenpx skills add toss/es-toolkit --skill guidegit clone --depth 1 https://github.com/toss/es-toolkitWhat 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.00048 | $0.00905 |
| Opus 5 | $0.00024 | $0.00452 |
| Sonnet 5 | $0.00010 | $0.00181 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
guide 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
es-toolkit Usage Guide
Provide guidance on installing, importing, and using es-toolkit across different runtimes.
Input
$ARGUMENTS — A topic or question about es-toolkit usage.
Why source-of-truth matters
Installation commands and import paths change across versions. When es-toolkit is already installed, verify its version and exports from the installed package. The skill may be installed as a standalone directory, so never assume the es-toolkit repository or a sibling docs directory is available.
Workflow
1. Inspect the user's project
Detect the package manager from its lockfile:
package-lock.json→ npmyarn.lock→ Yarnpnpm-lock.yaml→ pnpmbun.lockorbun.lockb→ Bun
If es-toolkit is installed, resolve its package metadata from the package that depends on it:
node -e "console.log(require.resolve('es-toolkit/package.json'))"
Run the command from the relevant workspace package, not automatically from a monorepo root. If the project uses Yarn Plug'n'Play, use yarn node instead of node. Read the resolved package.json to verify the installed version and its exports.
If the command fails because es-toolkit is not installed yet, continue with the installation guidance below; do not search for repository-relative files.
2. Answer based on the user's environment
Identify the runtime (Node.js, Bun, Deno, browser) and provide environment-specific guidance.
Stable setup facts:
- Deno:
deno add jsr:@es-toolkit/es-toolkit(note thejsr:prefix) - Deno import path:
'@es-toolkit/es-toolkit'(extra scope vs npm) - npm/yarn/pnpm/bun: Provide the command matching the detected package manager. If no lockfile exists, ask which package manager the user prefers or show the available commands.
- Import path:
'es-toolkit'for strict,'es-toolkit/compat'for lodash-compatible - Browser/CDN: jsdelivr and unpkg provide the UMD build (
_global), while esm.sh provides ES modules. Link to the official usage page below for current snippets.
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 · 77 lines · 48 tokens per session scan A b177221cff54
guide is a skill published in the GitHub repository toss/es-toolkit (11,316 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 905 once invoked, about $0.0002 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…