shift: Skill for Claude Code

.agents/skills/jsdoc/SKILL.md

jsdoc is a skill for Claude Code, Codex from shift-editor/shift. It costs 64 tokens per session (3,410 once invoked), scanned A, original, Apache-2.0.

A documentation skill for adding or updating JSDoc comments, which describe JavaScript or TypeScript code for its users and maintainers.

In plain words
What is it for?
It is for documenting exported classes, methods, constructors, data structures, rendering frames, and reactive state.
Why use it?
It helps API comments explain intent, side effects, ownership, lifetime, and whether values can be missing.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is shift-editor/shift's own configuration. It tells Claude Code and Codex how to work on shift itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything shift configures →

Reuse

Borrowing it

Nothing to install: this file belongs to shift-editor/shift. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/shift-editor/shift/main/.agents/skills/jsdoc/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/shift-editor/shift

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for jsdoc

README.md
[![agentmods](https://agentmods.dev/badge/skills/shift-editor/shift/jsdoc/github.svg)](https://agentmods.dev/skills/shift-editor/shift/jsdoc)
Your own site
<a href="https://agentmods.dev/skills/shift-editor/shift/jsdoc"><img src="https://agentmods.dev/badge/skills/shift-editor/shift/jsdoc/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.

agentmods 80×15 button for jsdoc

Your own site · 80×15
<a href="https://agentmods.dev/skills/shift-editor/shift/jsdoc"><img src="https://agentmods.dev/badge/skills/shift-editor/shift/jsdoc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,410 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00064 $0.03410
Opus 5.5 $0.00026 $0.01364
Sonnet 5.5 $0.00013 $0.00682
Haiku 4.5 $0.00006 $0.00341

Measured 1mo ago against content hash c592e3adc834, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

jsdoc 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.

.agents/skills/jsdoc/SKILL.md · 344 lines

How it starts

The opening of the file, as written. The whole thing — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/jsdoc — Source API Contracts

Write JSDoc as the stable public contract a caller needs without reading the implementation.

JSDoc comments must sit immediately before the documented symbol and use /** ... */ so tooling can parse them. Follow the standard tag vocabulary from https://jsdoc.app/about-getting-started, adapted for TypeScript source.

Why this matters

  • VS Code hover renders the first line in bold and the rest as body. A one-sentence contract on line 1 is the single highest-leverage thing you can write.
  • TypeScript already encodes shape. JSDoc is for what types can't say: ownership, lifetime, mutation, side effects, side-channel reactivity, nullability semantics, performance class, call ordering.
  • Code review is the second reader. Reviewers should be able to judge a call site against the doc without opening the implementation.

Runbook

  1. Identify the audience: caller, implementer, renderer, tool author, or maintainer.
  2. State the stable contract in one short opening sentence.
  3. Add details only for ownership, lifetime, reactivity, mutation, side effects, nullability, performance, or call ordering. Put long detail under @remarks.
  4. Use tags for callable APIs:
    • Add @param for every public constructor, method, or function parameter, and make the text describe the parameter's role, constraint, ownership, or valid range.
    • Add @returns when a method returns a value, nullable result, created object, snapshot, or read-only view.
    • Add @throws {ErrorType} when … for every observable failure mode (custom error class, semantic Error).
    • Do not add @returns void; describe the side effect in prose instead.
  5. Cross-reference siblings with @see {@link OtherSymbol} (one tag per related symbol).
  6. Add @example only when the intended call flow, ordering, or output is not obvious from the signature.
  7. Re-read the comment and delete implementation trivia, current call-site anecdotes, and unstable examples.

Hard Style Rules

Read the full file on GitHub · 344 lines

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.

  1. 1mo ago First seen · 344 lines · 64 tokens per session scan A c592e3adc834

Subscribe to this mod's changes

jsdoc is a skill published in the GitHub repository shift-editor/shift (379 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 3,410 once invoked, about $0.0003 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-09-01.

Related

Other skills, from other repositories

ax-rust-signature

Use when writing Rust code with axllm for string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes.

ax-llm/ax · 36 tokens

dd-code-generation

Use pup CLI for immediate Datadog operations or generate code for integration into applications.

DataDog/pup · 16 tokens

ax-rust-llm

Use when writing Rust code with axllm for using the generated Ax package, factory functions, package docs, examples, and API reference.

ax-llm/ax · 37 tokens

better-fullstack

Scaffold, plan, or extend Better Fullstack projects with the generator, CLI, or MCP server. Use when a user asks to create, generate, or scaffold a fullstack starter; choose a Better Fullstack stack; add Better Fullstack capabilities; compare agent scaffolding paths; or avoid hand-authoring boilerplate project files.

Marve10s/Better-Fullstack · 71 tokens

screenshot-studio

Regenerate the Pisper product screenshots under docs/shots/ against the current UI. Starts an isolated dev instance, seeds fictional demo data through the real runtime APIs, captures every referenced page at the exact 2558x1380 asset size, and replaces the files. Use only when the user asks to refresh product…

ling-kong-ran/pisper · 80 tokens

prompt-cache-optimizer

Audit and optimize Pisper system-prompt and tool-schema token overhead while preserving stable prompt-cache prefixes, permissions, and runtime behavior. Invoke only for explicit prompt or tool-context optimization work.

ling-kong-ran/pisper · 42 tokens