Borrowing it
Nothing to install: this file belongs to webjsdev/webjs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/webjsdev/webjs/main/.claude/skills/webjs-ready-for-dev/SKILL.mdgit clone --depth 1 https://github.com/webjsdev/webjsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/webjsdev/webjs/webjs-ready-for-dev)<a href="https://agentmods.dev/skills/webjsdev/webjs/webjs-ready-for-dev"><img src="https://agentmods.dev/badge/skills/webjsdev/webjs/webjs-ready-for-dev/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/webjsdev/webjs/webjs-ready-for-dev"><img src="https://agentmods.dev/badge/skills/webjsdev/webjs/webjs-ready-for-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 22 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
What 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.1 | $0.00029 | $0.04263 |
| Opus 5.5 | $0.00012 | $0.01705 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (27 stars, last pushed 13d ago), licensed MIT. It adds 29 tokens to every session and 4,263 once invoked, about $0.0001 per session on Opus 5.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
record-gotchas
Capture surprises, workarounds, and rough edges hit while consuming the public surface of Prisma 8, Prisma Compute, or Prisma Postgres — anything a real user of these products would experience. Fires whenever an operator (or agent) writes a workaround, hits a surprising failure mode, or finds undocumented behaviour…
swarm-plan
Full execution protocol for MODE: PLAN -- plan creation, external plan ingestion, QA gate persistence, task granularity, and traceability checks.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
orchestrator
Use when somebody asks for an orchestrator, a lead agent, a coordinator, or somebody to "keep an eye on" the agents working on a project — and when asking about who is minding a project, who is blocked, or what the orchestrator last said. Puts a seat in a project's chair inside agentglass (with its own rules, queue…
issue-ingest
Full execution protocol for MODE: ISSUEINGEST -- GitHub issue intake, localization, spec generation, and transition to the full fix workflow.
phase-wrap
Claude Code adapter for MODE: PHASE-WRAP. Delegates to the canonical opencode-swarm phase boundary protocol.