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/webjsdev/webjs/webjs-ready-for-devnpx skills add webjsdev/webjs --skill webjs-ready-for-devgit clone --depth 1 https://github.com/webjsdev/webjsWhat 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.00029 | $0.04263 |
| Opus 5 | $0.00015 | $0.02132 |
| Sonnet 5 | $0.00006 | $0.00853 |
| Haiku 4.5 | $0.00003 | $0.00426 |
Grade A, and why
webjs-ready-for-dev 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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Get tracked issues ready for development
"Ready for development" is a definition of done for PLANNING, not for code. An issue is ready when a cold AI agent, with zero access to the conversation that produced it, can implement it end to end without a discovery phase and without asking a single question.
This skill takes a list of issue numbers and, for each one in parallel, spawns a fully autonomous background agent that verifies the issue against the current codebase, settles every open call, rewrites the issue body into a complete plan, and moves the card to Ready on the project board.
Nothing here writes code. The deliverable is the issue body.
Inputs
- Issue numbers. Parse them from the prompt (
#1253,1253, "the low risk ones we listed"). If the user names a set from an earlier turn, use that set. - Nothing else is required. The skill is autonomous by design: it never asks the user to settle a design question, because settling those questions IS the work. Every call is decided from industry standard practice, the prior art in the sibling framework clones, and the repo's own conventions, and the plan records what settled it.
Steps
1. Read the board and the issue bodies
# The issue body and its comments, over REST.
gh api "repos/webjsdev/webjs/issues/<N>" --jq '.title, .body'
gh api "repos/webjsdev/webjs/issues/<N>/comments?per_page=100" --jq '.[].body'
Read the ISSUES, not the board. This skill is handed the issue numbers it is
readying, so it needs their bodies, and a whole-board dump answers a question
nobody asked at several hundred points of the GraphQL budget. When a card's
Status or item id is genuinely needed, take it from the issue node (step 5), not
from a dump. See .claude/gh-budget.md for the rule and the substitution table.
Most WebJs issues already carry a partial ## Implementation plan written when
they were filed. That is a starting point, not a finished plan. The agent's job
is to VERIFY it against the current code, complete every decision it left open,
and expand it to step level.
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 · 316 lines · 29 tokens per session scan A 0efe03e7c491
webjs-ready-for-dev is a skill published in the GitHub repository webjsdev/webjs (109 stars, last pushed 11d ago), licensed MIT. It adds 29 tokens to every session and 4,263 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
javascriptcore-garbage-collector
JSC GC reference for Bun. Use for use-after-free, JS object leaks, "collected too early", or when touching WriteBarrier, visitChildren, visitAdditionalChildren, JSRef, JSC::Strong/Weak, hasPendingActivity, ensureStillAlive, addOpaqueRoot, reportExtraMemoryAllocated, IsoSubspace, HeapAnalyzer, finalize.
implementing-jsc-classes-cpp
Implements JavaScript classes in C++ using JavaScriptCore. Use when creating new JS classes with C++ bindings, prototypes, or constructors.
implementing-jsc-classes-rust
Creates JavaScript classes using Bun's Rust bindings generator (.classes.ts). Use when implementing new JS APIs in Rust with JSC integration, prototypes, or constructors.
rust-system-calls
Guides using bunsys for system calls and file I/O in Rust. Use when implementing file operations, opening fds, or any syscall path instead of std::fs or libc.
slowest-tests
Find the top-N slowest test files in CI from a recent BuildKite run, optionally posting the results to a Slack channel as a formatted table. Use when asked to find slow CI tests, "what's making CI slow", or to post a slow-test report to Slack.
writing-bundler-tests
Guides writing bundler tests using itBundled/expectBundled in test/bundler/. Use when creating or modifying bundler, transpiler, or code transformation tests.