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.
npx agentmods add commands/insight-services-apac/ingenious/jsdocgit clone --depth 1 https://github.com/Insight-Services-APAC/ingeniousWrote 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/commands/insight-services-apac/ingenious/jsdoc)<a href="https://agentmods.dev/commands/insight-services-apac/ingenious/jsdoc"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/jsdoc.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.00000 | $0.00858 |
| Opus 5 | $0.00000 | $0.00429 |
| Sonnet 5 | $0.00000 | $0.00172 |
| Haiku 4.5 | $0.00000 | $0.00086 |
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 yesterday.
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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify and Fix JSDoc Comments with ESLint
Use ESLint JSDoc plugin to ensure all functions, classes, and modules have proper, consistent documentation.
CRITICAL: Persistence Requirement
DO NOT STOP until ALL JSDoc issues are resolved. This task requires complete coverage:
- Process every single file reported by the tools
- Fix every missing or malformed JSDoc comment
- Continue working through all modules systematically
- Re-run the analysis tools after each batch of fixes to confirm progress
- Only consider this task complete when ESLint reports zero JSDoc violations
If context window limits approach, document remaining files in the todo list and continue in the next session. Do not leave the codebase in a partially documented state.
1. Install JSDoc Plugin (if missing)
npm install -D eslint-plugin-jsdoc
2. Configure ESLint
Add to .eslintrc.js:
{
plugins: ['jsdoc'],
extends: ['plugin:jsdoc/recommended-typescript'],
rules: {
'jsdoc/require-jsdoc': ['warn', {
require: {
FunctionDeclaration: true,
MethodDefinition: true,
ClassDeclaration: true,
ArrowFunctionExpression: false,
FunctionExpression: false
}
}],
'jsdoc/require-description': 'warn',
'jsdoc/require-param-description': 'warn',
'jsdoc/require-returns-description': 'warn'
}
}
3. Run JSDoc Analysis
npx eslint . --ext .js,.ts,.vue --rule 'jsdoc/require-jsdoc: warn'
4. JSDoc Standards
Use consistent JSDoc format:
/**
* Short one-line summary ending with period.
*
* Longer description if needed. Explain the purpose,
* not the implementation.
*
* @param param1 - Description of first parameter.
* @param param2 - Description of second parameter.
* @returns Description of return value.
* @throws {Error} When param2 is negative.
*
* @example
* ```ts
* const result = functionName('value', 42);
* ```
*/
function functionName(param1: string, param2: number): boolean {
// ...
}
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.
- yesterday First seen · 145 lines · 0 tokens per session scan A 44153394b851
jsdoc is a command published in the GitHub repository Insight-Services-APAC/ingenious (24 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 858 tokens. 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-04.
Other commands, from other repositories
doc
Command "doc" from echoVic/blade-code, covering 目标文件, 文档规范, typescript/javascript, 类和接口 and 要求.
react
Apply React with TypeScript best practices.
typescript
Apply TypeScript best practices and coding standards.
vue3
Apply Vue 3 with TypeScript and Composition API patterns.
generate-types
Generate TypeScript types or type definitions from schemas, APIs, or data structures.
scaffold-nextjs
Scaffold a basic Next.js 15 project with modern best practices.