nextjs-tsdoc-documentor

nextjs-tsdoc-documentor is a skill for Claude Code, Codex from darellchua2/opencode-config-template. It costs 40 tokens per session (3,951 once invoked), scanned A, original, Apache-2.0.

A TSDoc documentation helper for TypeScript functions in Next.js projects. TSDoc is a comment format that documents parameters, return values, and other code details for developers and tools.

In plain words
What is it for?
Use it to document new or existing functions, React components, utilities, asynchronous functions, parameters, and return values.
Why use it?
It fills in missing or incomplete documentation while following the project's existing style. This makes function behavior and types easier to understand in code reviews and editors.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/darellchua2/opencode-config-template/nextjs-tsdoc-documentor
Any agent
npx skills add darellchua2/opencode-config-template --skill nextjs-tsdoc-documentor
Clone the repo
git clone --depth 1 https://github.com/darellchua2/opencode-config-template

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 nextjs-tsdoc-documentor

README.md
[![agentmods](https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/nextjs-tsdoc-documentor.svg)](https://agentmods.dev/skills/darellchua2/opencode-config-template/nextjs-tsdoc-documentor)
Your own site
<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/nextjs-tsdoc-documentor"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/nextjs-tsdoc-documentor.svg" alt="Measured on agentmods" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,951 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 $0.00040 $0.03951
Opus 5 $0.00020 $0.01975
Sonnet 5 $0.00008 $0.00790
Haiku 4.5 $0.00004 $0.00395

Measured 4d ago against content hash 9690c54c4841, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

nextjs-tsdoc-documentor 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 4d 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.

opencode_app/.opencode/skills/_archived/nextjs-tsdoc-documentor/SKILL.md · 668 lines

How it starts

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

What this skill does

  • Adds TSDoc comments to all TypeScript functions in Next.js projects
  • Ensures all functions with parameters have proper @param tags with type information
  • Documents return values with @returns tags
  • Handles async functions, React components, and utility functions
  • Maintains existing TSDoc style conventions in the codebase
  • Follows TSDoc standards for TypeScript code documentation
  • Integrates with TypeScript's type system for better IDE support

When to use

Use this when:

  • Implementing new functions, components, or utility modules in Next.js TypeScript projects
  • Refactoring code and adding missing documentation
  • Preparing for code review and ensuring proper TSDoc documentation standards
  • Functions lack TSDoc comments or have incomplete parameter documentation
  • You need to enforce TSDoc presence as part of quality checks

Common signals:

  • TypeScript functions without TSDoc comments
  • Functions with parameters but missing @param tags
  • Return values not documented with @returns
  • Async functions without proper @returns Promise<T> documentation
  • TypeScript code lacking type-aware documentation

TSDoc Standard Format

Basic Function

/**
 * Calculate the sum of two numbers.
 *
 * @param a - The first number to add
 * @param b - The second number to add
 * @returns The sum of a and b
 */
function calculateSum(a: number, b: number): number {
  return a + b;
}

Async Function

/**
 * Fetch user data from the API.
 *
 * @param userId - The unique identifier of user
 * @returns A promise that resolves to the user data
 * @throws When the API request fails
 */
async function fetchUser(userId: string): Promise<User> {
  const response = await fetch(`/api/users/${userId}`);
  if (!response.ok) {
    throw new Error('Failed to fetch user');
  }
  return response.json();
}

React Component

/**
 * UserProfile component displays user information.
 *
 * @param props - Component properties
 * @param props.userId - The user's unique identifier
 * @param props.onEdit - Callback when edit button is clicked
 * @returns A React component rendering user profile
 */
export function UserProfile({ userId, onEdit }: UserProfileProps) {
  // Component implementation
}

Read the full file on GitHub · 668 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. 4d ago First seen · 668 lines · 40 tokens per session scan A 9690c54c4841

Subscribe to this mod's changes

nextjs-tsdoc-documentor is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 40 tokens to every session and 3,951 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens