comments

comments is a skill for Claude Code from fubits1/svelte-skills. It costs 47 tokens per session (2,219 once invoked), scanned A, original, MIT.

A rulebook for writing, keeping, moving, or deleting code comments, documentation strings, and TODO notes across programming languages.

In plain words
What is it for?
Use it when editing source files, reviewing comments, or placing TODOs and documentation strings.
Why use it?
It prevents comments that merely repeat the code and defines which comments, formats, and required notes should remain.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: reads .claude/ paths.

Part of the frontend plugin — 13 skills shipped together

Good fit Use it when editing source files, reviewing comments, or placing TODOs and documentation strings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fubits1/svelte-skills/comments
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.

Any agent
npx skills add fubits1/svelte-skills --skill comments
Clone the repo
git clone --depth 1 https://github.com/fubits1/svelte-skills

Made for: Claude Code.

Or install frontend, the plugin that ships this one along with the rest of its 13 skills.

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 comments

README.md
[![agentmods](https://agentmods.dev/badge/skills/fubits1/svelte-skills/comments/github.svg)](https://agentmods.dev/skills/fubits1/svelte-skills/comments)
Your own site
<a href="https://agentmods.dev/skills/fubits1/svelte-skills/comments"><img src="https://agentmods.dev/badge/skills/fubits1/svelte-skills/comments/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.

agentmods 80×15 button for comments

Your own site · 80×15
<a href="https://agentmods.dev/skills/fubits1/svelte-skills/comments"><img src="https://agentmods.dev/badge/skills/fubits1/svelte-skills/comments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,219 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00047 $0.02219
Opus 5.5 $0.00019 $0.00888
Sonnet 5.5 $0.00009 $0.00444
Haiku 4.5 $0.00005 $0.00222

Measured 11d ago against content hash de5a47dc3991, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

comments 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 11d 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/frontend/skills/comments/SKILL.md · 139 lines

How it starts

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

Comments

REQUIRED SUB-SKILL: deslop, from stephenturner/skill-deslop (MIT). If it isn't installed, stop and ask the user to install it: git clone https://github.com/stephenturner/skill-deslop.git ~/.claude/skills/deslop. Where deslop and this skill disagree, this skill wins: deslop's "we" loses to the we use ban, for example.

Don't apply this skill from memory. It covers //, /* */, /** */, #, docstrings and <!-- -->.

Which comments you judge

  • Your comments default to DELETE. The survival test, Format and the ban-list judge only the comments you add in this task. A comment you add earns its place by the survival test, or it goes. The code already says WHAT, so a comment merely restating WHAT is noise. Default-DELETE removes only noise.

  • A comment someone else requires skips the survival test and takes the syntax and format they define. The ban-list still applies to the wording you choose, and any reason you give with it must pass the survival test. Required comments are:

    • a specific comment the user asks for
    • a docstring style the project's linter enforces
    • a comment another skill requires, such as the @component block and prop JSDoc (svelte-5:code-style-svelte, svelte-5:doc-component)
    • a tool directive such as eslint-disable-next-line; whether a directive is allowed at all is frontend:editing's rule
  • Existing comments stay, with all their information. A comment that was in the file before this task started is not yours to judge or reformat, even when it looks redundant. Never turn its /** */ block into // lines. NEVER remove information from it, not with Write, not with Edit, not ever. Information means:

    • a HINT/TODO/FIXME keyword
    • a cross-reference
    • a non-obvious WHY
    • a marker such as # v26.12.1

    Unless the user asks for a specific change, you may change it in four ways only; the first is mandatory:

    • fix the part your change made false, or remove the comment if your change made all of it false
    • append (don't replace) a fact your change requires, in the comment's own style
    • fix what the project's linter reports on it, keeping all its information
    • delete it together with the code it describes

Read the full file on GitHub · 139 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. 11d ago First seen · 139 lines · 47 tokens per session scan A de5a47dc3991

Subscribe to this mod's changes

comments is a skill published in the GitHub repository fubits1/svelte-skills (10 stars, last pushed 12d ago), licensed MIT. It adds 47 tokens to every session and 2,219 once invoked, about $0.0002 per session on Opus 5.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-10-27.

Related

comments compared with skills from other repositories

comments next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
commentsfubits1/svelte-skillsSkill1012d agoMITA47Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code