jsdoc-review

jsdoc-review is a command for Claude Code from pau-vega/Devkit-AI. It costs 52 tokens per session (463 once invoked), scanned A, original, MIT.

A command that checks TypeScript files for required JSDoc comments, which are documentation notes written inside source code. It can review changed files or a specified path at minimal, standard, or strict enforcement levels.

In plain words
What is it for?
Use it to review changed TypeScript files, inspect a particular directory, and report JSDoc issues under the selected enforcement level.
Why use it?
It finds missing or incomplete code documentation before it becomes inconsistent across a project. It also applies a chosen level of documentation requirements.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the jsdoc-standards plugin — 1 skill, 1 command, 1 agent, 1 hook shipped together

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add pau-vega/Devkit-AI
Claude Code
/plugin install jsdoc-standards

Made for: Claude Code.

Or install jsdoc-standards, the plugin that ships this one along with the rest of its 1 skill, 1 command, 1 agent, 1 hook.

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-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/pau-vega/devkit-ai/jsdoc-review.svg)](https://agentmods.dev/commands/pau-vega/devkit-ai/jsdoc-review)
Your own site
<a href="https://agentmods.dev/commands/pau-vega/devkit-ai/jsdoc-review"><img src="https://agentmods.dev/badge/commands/pau-vega/devkit-ai/jsdoc-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 463 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00052 $0.00463
Opus 5 $0.00026 $0.00231
Sonnet 5 $0.00010 $0.00093
Haiku 4.5 $0.00005 $0.00046

Measured 6d ago against content hash ba0579d5ffc9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

jsdoc-review 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 6d 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.

plugins/jsdoc-standards/commands/jsdoc-review.md · 44 lines

What it actually says

JSDoc Review

Dispatch the jsdoc-reviewer agent to audit TypeScript files for JSDoc compliance.

Arguments: $ARGUMENTS

Argument Parsing

Parse the arguments to extract the enforcement level and optional path:

  • No arguments — use standard level, review changed files
  • Level only (e.g., strict) — use that level, review changed files
  • Level and path (e.g., standard src/utils) — use that level, review files at path
  • Path only (e.g., src/utils) — use standard level, review files at path

Valid levels: minimal, standard, strict.

Execution

  1. Load the jsdoc-conventions skill from ${CLAUDE_PLUGIN_ROOT}/skills/jsdoc-conventions/SKILL.md to get the full rule set
  2. Determine the enforcement level from arguments (default: standard)
  3. Discover target .ts and .tsx files:
    • If a path was provided, glob for files at that path
    • If no path, run git diff --name-only HEAD to find changed files
    • If no uncommitted changes, run git diff --name-only HEAD~1 for the last commit
    • Filter for .ts and .tsx files only
  4. Read each file and check against the rules for the selected level
  5. Report findings grouped by file, using severity levels:
    • Error — Required JSDoc is completely missing
    • Warning — JSDoc is present but incomplete or malformed for the level
    • Suggestion — Opportunity to improve documentation quality
  6. End with a summary: total files reviewed, errors, warnings, suggestions, and the level used
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. 6d ago First seen · 44 lines · 52 tokens per session scan A ba0579d5ffc9

Subscribe to this mod's changes

jsdoc-review is a command published in the GitHub repository pau-vega/Devkit-AI (2 stars, last pushed 21d ago), licensed MIT. It adds 52 tokens to every session and 463 once invoked, about $0.0003 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-31.