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/skilld-dev/skilld/generate-package-skillnpx skills add skilld-dev/skilld --skill generate-package-skillgit clone --depth 1 https://github.com/skilld-dev/skilldWhat 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.00025 | $0.00464 |
| Opus 5 | $0.00013 | $0.00232 |
| Sonnet 5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
generate-package-skill 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a package Skill
Create a focused Skill that helps an Agent use one package correctly.
Inputs
Ask for a package name, package directory, or prepared package source. Ask for the destination only when the request does not provide one.
Research
- Record the exact installed or prepared package version.
- Read the package manifest and every exported entry point.
- Read public type entry points and their source definitions.
- Read current official documentation and runnable examples.
- Check release notes and migration guides for the exact version.
- Prefer public exports over internal files.
- Record advice only when the prepared source or official documentation proves it.
For an npm package, use the installed or prepared package source first.
Use current official documentation when the prepared source lacks required details.
For each version-specific rule, cite the source path or official documentation URL.
Use path:line citations for prepared source when line numbers add value.
Output
Write one directory whose name matches the Skill name.
The directory must contain SKILL.md.
Put detailed or conditional material in references/.
Put reusable commands or code in scripts/ when execution adds value.
The SKILL.md frontmatter must contain only:
---
name: package-name
description: Clear trigger conditions and the result this Skill provides.
---
Use lowercase letters, numbers, and single hyphens in the name. Keep the name at 64 characters or fewer. Keep the description at 1024 characters or fewer.
Quality checks
- Keep instructions specific to the package.
- Use current APIs and package vocabulary.
- Include small examples for common tasks.
- State environment or version limits.
- Cite public APIs, version limits, and migration advice.
- Link each reference from
SKILL.md. - Remove generated filler and repeated prose.
- Do not copy large documentation sections.
- Do not include credentials, caches, build output, or dependency directories.
What ships with it
1 file 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 · 65 lines · 25 tokens per session scan A 2e6ab4e7994d
generate-package-skill is a skill published in the GitHub repository skilld-dev/skilld (306 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 464 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-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…