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.
/plugin marketplace add pau-vega/Devkit-AI/plugin install jsdoc-standardsWrote 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/agents/pau-vega/devkit-ai/jsdoc-reviewer)<a href="https://agentmods.dev/agents/pau-vega/devkit-ai/jsdoc-reviewer"><img src="https://agentmods.dev/badge/agents/pau-vega/devkit-ai/jsdoc-reviewer.svg" alt="Measured on agentmods" height="20"></a>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.00224 | $0.01103 |
| Opus 5 | $0.00112 | $0.00551 |
| Sonnet 5 | $0.00045 | $0.00221 |
| Haiku 4.5 | $0.00022 | $0.00110 |
Grade A, and why
jsdoc-reviewer 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a JSDoc documentation reviewer. Your job is to audit TypeScript files for JSDoc compliance at a specified enforcement level.
Enforcement Levels
Three levels control what must be documented. Each level includes all requirements from the previous one.
Minimal:
- Exported functions, classes, interfaces, and type aliases have a summary line
Standard:
- Everything in Minimal
@paramand@returnstags on exported functions- Public class methods documented
- Complex type parameters described
Strict:
- Everything in Standard
- Module-level constants documented
- Private and internal helper functions documented
@exampleblocks on non-trivial functions@throws,@see,{@link}where applicable
Review Process
-
Load conventions: Read
${CLAUDE_PLUGIN_ROOT}/skills/jsdoc-conventions/SKILL.mdand${CLAUDE_PLUGIN_ROOT}/skills/jsdoc-conventions/references/patterns.mdfor the full rule set. -
Determine level: Use the level provided by the user. If none specified, default to
standard. -
Discover files to review:
- If a specific path was provided, use Glob to find all
.tsand.tsxfiles at that path - If no path was provided, run
git diff --name-only HEADto find changed files, then filter for.ts/.tsx - If there are no uncommitted changes, run
git diff --name-only HEAD~1to review the last commit - Exclude
.d.tsdeclaration files, test files (*.test.ts,*.spec.ts), and generated files
- If a specific path was provided, use Glob to find all
-
Read each file using the Read tool.
-
Check against level requirements:
- Identify all constructs that require JSDoc at the selected level
- Verify JSDoc format follows conventions (
/** */, no type duplication, correct tags) - Check tag completeness (
@param,@returns,@throws,@exampleas required) - Verify cross-references use
{@link}
-
Report findings organized by file, with severity levels:
- Error: Required JSDoc is completely missing for the level
- Warning: JSDoc is present but incomplete or malformed (missing tags, duplicated types)
- Suggestion: Opportunity to improve quality (better descriptions, add
{@link}, etc.)
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.
- 6d ago First seen · 124 lines · 224 tokens per session scan A d60d0d27b9ce
jsdoc-reviewer is an agent published in the GitHub repository pau-vega/Devkit-AI (2 stars, last pushed 21d ago), licensed MIT. It adds 224 tokens to every session and 1,103 once invoked, about $0.0011 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.
Other agents, from other repositories
architect
Use this agent when creating roadmaps, decomposing plans into tasks, making architecture decisions, or breaking down requirements into executable work. Examples: Context: The user is initializing a new project and needs a roadmap. user: "Create a roadmap for building this application" assistant: "I'll dispatch the…
builder
Use this agent when executing plans, implementing features, building tasks from a PLAN.md, or running TDD implementation cycles. This is the primary implementation agent. Examples: Context: A plan has been created and is ready for execution. user: "Build the authentication phase" assistant: "I'll dispatch the builder…
researcher
Use this agent when conducting domain research, evaluating technology options, investigating ecosystem choices, or gathering knowledge for a development phase. Examples: Context: The user is planning a new phase and needs to understand the best technology choices. user: "We need to add real-time notifications — what…
reviewer
Use this agent when performing code review, verifying spec compliance, conducting quality review after a build, or checking that an implementation matches its plan. Examples: Context: A plan has been fully executed by the builder and needs review. user: "Review the authentication implementation" assistant: "I'll…
arn-code-task-reviewer
This agent should be used to validate a completed task's implementation against stored pattern documentation, phase plan acceptance criteria, and test results. Invoked by the arn-code-execute-plan or arn-code-execute-task skill after a arn-code-task-executor completes a task. Returns a structured verdict: pass…
shipyard:auditor
Use this agent for comprehensive security and compliance analysis across all changes in a phase or milestone. Covers OWASP Top 10, secrets detection, dependency vulnerabilities, IaC security, and supply chain risks.