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 skills add Netcracker/qubership-ai-packages --skill jsdoc-authoringgit clone --depth 1 https://github.com/Netcracker/qubership-ai-packagesWrote 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/skills/netcracker/qubership-ai-packages/jsdoc-authoring)<a href="https://agentmods.dev/skills/netcracker/qubership-ai-packages/jsdoc-authoring"><img src="https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/jsdoc-authoring/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.
<a href="https://agentmods.dev/skills/netcracker/qubership-ai-packages/jsdoc-authoring"><img src="https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/jsdoc-authoring.svg" alt="Reviewed on agentmods" width="80" 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.00221 | $0.15776 |
| Opus 5 | $0.00111 | $0.07888 |
| Sonnet 5 | $0.00044 | $0.03155 |
| Haiku 4.5 | $0.00022 | $0.01578 |
Grade A, and why
jsdoc-authoring 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 today.
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 — 928 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring a JSDoc or TSDoc comment
This skill governs what a comment says and in what order. Wording, tone, sentence length, and dialect belong to
english-developer-style: load it too, and defer to it on the prose. The two compose: this skill picks the slots; that
one writes the sentences.
It covers both languages, because they share one comment syntax, one tag vocabulary, one Markdown body, and one language
service behind the editor hover where most readers meet the comment. TSDoc is the standardized subset that API Extractor
and TypeDoc read; JSDoc is the older, looser superset. Where a rule differs between the two dialects, this file says so.
One rule differs between a .ts file and a checked .js file, and it inverts: that is §3a, the most important section
here for an agent that writes both.
Conventions carried in from another language's doc comments go wrong in three places, so do not translate them in your head: the summary ends at the first block tag rather than at the first period (§3), Markdown is the markup (§5), and a tag that states a type is either redundant or the code itself, depending on the file it sits in (§3a, §6).
The formatter does not own the layout. Measured on Prettier 3.9.6, a doc comment is re-indented to a single leading
* column and otherwise left alone: prose is not reflowed, inner runs of spaces are not collapsed, and a line past
--print-width is not wrapped. Every line break inside a doc comment is your decision, and it survives every format
run, including the stale ones.
1. The correction that matters most
"Document the why, not the what" is half wrong for a doc comment, and the wrong half does the damage.
An inline // comment documents the why; it sits next to code the reader can already see. A doc comment documents
the contract: what a caller may rely on, what an implementer must guarantee, what holds before and after. That is a
what at the level of a promise, not a restatement of the code.
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.
- today Changed · -17 lines 532ac1c69ac5
- 5d ago Changed · +180 lines · -5 tokens per session 28d9bceef7b7
- 10d ago First seen · 765 lines · 226 tokens per session scan A e86ec3a18316
jsdoc-authoring is a skill published in the GitHub repository Netcracker/qubership-ai-packages (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 221 tokens to every session and 15,776 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 skills, from other repositories
no-bare-casts
Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.
aws-sst-development
SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework.
league-akari-shard-development
Use when creating, extending, refactoring, splitting, or reviewing League Akari main or renderer shards, including shard file organization, controller/loader/executor/handler boundaries, naming conventions, renderer TSX usage, platform guards, and public contract compatibility.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
migrate-better-result-3
Migrate a TypeScript codebase from better-result 2.x to 3.0. Use when upgrading better-result across the TaggedError syntax, removed Result serialization helpers, recovery inference, matching, or retry APIs.