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-doc-sync/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-doc-sync)<a href="https://agentmods.dev/skills/webjsdev/webjs/webjs-doc-sync"><img src="https://agentmods.dev/badge/skills/webjsdev/webjs/webjs-doc-sync/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-doc-sync"><img src="https://agentmods.dev/badge/skills/webjsdev/webjs/webjs-doc-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00160 | $0.02215 |
| Opus 5.5 | $0.00064 | $0.00886 |
| Sonnet 5.5 | $0.00032 | $0.00443 |
| Haiku 4.5 | $0.00016 | $0.00221 |
Grade A, and why
webjs-doc-sync 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Keep every webjs doc surface in sync with shipped behaviour
WebJs ships its documentation across SEVERAL independent surfaces. The recurring
failure mode is updating ONE (usually AGENTS.md) and silently missing the rest,
so the docs site, the marketing website, and the scaffold's per-agent rule files
drift behind the framework. HTTP-verb server actions (#488) shipped with
AGENTS.md updated but the docs site untouched, which is exactly the gap this
skill exists to close.
This skill is the authoritative map of every surface plus a deterministic change-type to surface mapping. Use it in two modes: per-change sync (a feature just shipped, bring docs in line) and audit (sweep already-shipped work for drift and file follow-ups).
The complete doc surface map
Treat this list as the universe. For any change, decide per surface whether it applies, then update or consciously skip each.
AGENTS.md(repo root) plus the skill at.agents/skills/webjs/(SKILL.md plus its 13references/:routing-and-pages,components,data-and-actions,auth-and-sessions,styling,client-router-and-streaming,optimistic-ui,typescript,testing,built-ins,runtime,service-worker,muscle-memory-gotchas).AGENTS.mdstays lean and points at the matchingreferences/<x>.mdfor the full reference. A new public API goes in BOTH theAGENTS.mdsummary and the relevantreferences/file.README.md(repo root). Update when a headline capability changes (the feature list, the quickstart, the runtime/template matrix).- The docs site:
website/app/docs/<topic>/page.ts. This is the user-facing documentation at webjs.dev/docs. Find the topic page(s) that cover the area (server-actions,routing,components,caching,configuration,client-router,data-fetching, ...) and update them.llms.txt/llms-full.txtare generated LIVE from the doc pages (no build step), so they never need a manual edit. A brand-new capability may need a NEW topic page plus a nav entry. - The marketing website:
website/. Update landing/feature copy when a headline capability changes. The changelog (website/app/changelog) is auto-generated from conventional PR titles, so NEVER hand-write it; the blog is manual. - The scaffold templates:
packages/cli/templates/. Every new app ships these. The scaffold is single-source:AGENTS.md(a thin pointer) plus the one cross-agent skill at.agents/skills/webjs/(SKILL.md +references/) that every tool reads. There are no per-agent rule files to keep in lockstep. A change to how apps are AUTHORED lands in the skill. When the change is to whatwebjs createGENERATES (a gallery/showcase demo, a template, the generated layout/home/theme/schema, a scaffold convention), this surface has more parts (thepackages/cli/lib/*generators, the repo-rootgallery/**app whose demos prepack bundles into the CLI, the scaffold tests, the framework template-matrix docs, the preview apps) and a mandatorygenerate + boot + webjs checkstep: use the dedicatedwebjs-scaffold-syncskill for those, and treat this doc-sync entry as the docs-only slice. The CLI help text inpackages/cli/is part of this surface for a new command or flag. - Example / dogfood apps (
examples/blog/CONVENTIONS.mdand friends). Update when a convention the example demonstrates changes.
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 · 137 lines · 160 tokens per session scan A 26897e1c63a9
webjs-doc-sync is a skill published in the GitHub repository webjsdev/webjs (27 stars, last pushed 13d ago), licensed MIT. It adds 160 tokens to every session and 2,215 once invoked, about $0.0006 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
hono-core
Hono ultrafast web framework fundamentals - routing, context, handlers, and response patterns for multi-runtime deployment.
htmx-alpine-frontend
Build a no-build-step interactive frontend with HTMX partial swaps and Alpine.js state, served from CDN over server-rendered Jinja pages.
bun
Bun all-in-one JavaScript runtime and toolkit reference. Covers runtime APIs (file I/O, HTTP server, SQLite, shell), ultra-fast package manager, built-in bundler with plugins, test runner with mocking, TypeScript support, and Node.js compatibility.
Node.js Debugger
Use this skill when debugging runtime failures in Node.js or Bun: stack traces, async errors, startup crashes, port conflicts, and memory leaks.
Bun Patterns
Use this skill when working in Bun-based projects (or Node projects running on Bun) and you want reliable runtime expectations, dependency management, and debugging workflows.
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.