pixiv-cli-code-commenting

pixiv-cli-code-commenting is a skill for Codex from FlanChanXwO/pixiv-cli. It costs 80 tokens per session (1,781 once invoked), scanned A, original, MIT.

A code-documentation guide for writing and reviewing comments, API descriptions, docstrings, and numbered workflow steps. It focuses on recording intent, caller expectations, limits, and rules that the code alone does not show.

In plain words
What is it for?
Use it when changing a non-obvious rule, public interface, invariant, or multi-stage function in pixiv-cli. It supports reviewing comments across the CLI, SDK, and MCP layers without duplicating the same explanation everywhere.
Why use it?
It helps prevent comments that merely repeat the code, while keeping important explanations accurate when behavior or contracts change. It also helps identify and remove stale or misleading comments.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

Good fit Use it when changing a non-obvious rule, public interface, invariant, or multi-stage function in pixiv-cli. It supports reviewing comments across the CLI, SDK, and MCP layers without duplicating the same explanation everywhere.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/flanchanxwo/pixiv-cli/pixiv-cli-code-commenting
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 FlanChanXwO/pixiv-cli --skill pixiv-cli-code-commenting
Clone the repo
git clone --depth 1 https://github.com/FlanChanXwO/pixiv-cli

Made for: 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 pixiv-cli-code-commenting

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/flanchanxwo/pixiv-cli/pixiv-cli-code-commenting"><img src="https://agentmods.dev/badge/skills/flanchanxwo/pixiv-cli/pixiv-cli-code-commenting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,781 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.00080 $0.01781
Opus 5.5 $0.00032 $0.00712
Sonnet 5.5 $0.00016 $0.00356
Haiku 4.5 $0.00008 $0.00178

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

Security

Grade A, and why

pixiv-cli-code-commenting 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 22d 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.

.agents/skills/pixiv-cli-code-commenting/SKILL.md · 96 lines

How it starts

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

pixiv-cli Code Commenting

Expose information that names and structure cannot express clearly: caller contracts, intent, constraints, invariants, and meaningful workflow stages. Optimize understanding, not comment count or code length.

Repository context

Read root AGENTS.md and the affected owner before editing. This checked-in skill is self-contained; it does not require the personal code-commenting skill. Review caller contracts across CLI, SDK, and MCP without duplicating them in every layer. Keep machine-output, credential, transaction outcome, and Rust/cgo ownership comments precise; an ordinary prose cleanup must not change build directives or the cgo preamble. Use pixiv-cli-test for verification scope and pixiv-cli-develop for any authorized structural change.

Editing workflow

  1. Read the affected symbol, enclosing flow, nearby comments, and applicable repository conventions. Inspect callers or tests when a claimed contract is unclear; do not infer thread safety, atomicity, retry safety, or ownership from a name.
  2. Identify the missing information before adding prose. Keep accurate contract and intent comments, correct stale ones, and remove narration that adds no information. Leaving self-explanatory code uncommented is a valid outcome.
  3. Choose the nearest useful location: API documentation for a caller contract, a type/field comment for an invariant or unit, an inline comment for a surprising choice, or numbered comments for a meaningful multi-stage flow.
  4. Keep edits within the requested scope. A comment review is not permission to rename APIs, extract helpers, redesign modules, add tests, or introduce dependencies. Report structural or behavioral defects separately unless their correction is authorized.
  5. Re-read comments against the final code and applicable documentation output. Confirm stage order, symbol references, factual guarantees, and protected directives. Report uncertain claims rather than documenting them as facts.

Read the full file on GitHub · 96 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 22d ago First seen · 96 lines · 80 tokens per session scan A 544089f9a4f5

Subscribe to this mod's changes

pixiv-cli-code-commenting is a skill published in the GitHub repository FlanChanXwO/pixiv-cli (134 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 1,781 once invoked, about $0.0003 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-09-24.

Related

Other skills, from other repositories

manage-llm-server

Inspect and control the local LLM server(s) via llama-launcher — list profiles, see what's running, switch models, tail logs. Use when the user wants to know what model is loaded, change models, start/stop or restart the server, or troubleshoot a stuck load.

airiclenz/llama-launcher · 66 tokens

gh-skill

Manage agent skills with gh skill. Use this skill to discover, preview, install, update, and publish Agent Skills so an agent can self-manage the skills available in its environment.

cli/cli · 41 tokens

printing-press-amend

Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…

mvanhorn/cli-printing-press · 222 tokens

voiden

Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.

VoidenHQ/voiden · 28 tokens

octo-drive

Octo Drive — spaces, folders, file upload/download, online-document mounts, share links, invites, IM-attachment transfer. Works with a bot token or a user API key; the CLI routes by token kind. Load after octo-shared.

Mininglamp-OSS/octo-cli · 55 tokens

octo-mail

OCTO Agent Mail operations for reading, searching, policy-aware sending, preparing drafts, and checking delivery status exclusively through octo-cli.

Mininglamp-OSS/octo-cli · 32 tokens