NoizuPromptLingo: Skill for Claude Code

.agents/skills/source-command-annotate/SKILL.md

source-command-annotate is a skill for Claude Code, Codex from noizu-labs-ml/NoizuPromptLingo. It costs 58 tokens per session (1,662 once invoked), scanned A, original, MIT.

A tool that adds footnote markers and definitions without changing the original file. It writes an annotated copy and a separate footnotes file.

In plain words
What is it for?
Use it to annotate source files with footnotes, keeping the annotations and their definitions in separate generated files.
Why use it?
It preserves the source while ensuring every inserted marker has a matching explanation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is noizu-labs-ml/NoizuPromptLingo's own configuration. It tells Claude Code and Codex how to work on NoizuPromptLingo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything NoizuPromptLingo configures →

Reuse

Borrowing it

Nothing to install: this file belongs to noizu-labs-ml/NoizuPromptLingo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/noizu-labs-ml/NoizuPromptLingo/main/.agents/skills/source-command-annotate/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/noizu-labs-ml/NoizuPromptLingo

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 source-command-annotate

README.md
[![agentmods](https://agentmods.dev/badge/skills/noizu-labs-ml/noizupromptlingo/source-command-annotate.svg)](https://agentmods.dev/skills/noizu-labs-ml/noizupromptlingo/source-command-annotate)
Your own site
<a href="https://agentmods.dev/skills/noizu-labs-ml/noizupromptlingo/source-command-annotate"><img src="https://agentmods.dev/badge/skills/noizu-labs-ml/noizupromptlingo/source-command-annotate.svg" alt="Measured on agentmods" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,662 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.00058 $0.01662
Opus 5 $0.00029 $0.00831
Sonnet 5 $0.00012 $0.00332
Haiku 4.5 $0.00006 $0.00166

Measured yesterday against content hash 30b7cdcbfe75, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

source-command-annotate 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.

.agents/skills/source-command-annotate/SKILL.md · 283 lines

How it starts

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

source-command-annotate

Use this skill when the user asks to run the migrated source command annotate.

Command Template

Annotation Instructions.

THE ANNOTATION LOOP

For each annotation, perform these two operations in sequence before moving to the next annotation:

┌─────────────────────────────────────────────────────────────┐
│                                                             │
│   FOR EACH ANNOTATION:                                      │
│                                                             │
│      1. Insert [^marker] in annotated file                  │
│      2. Append [^marker]: definition to footnotes file      │
│                                                             │
│   THEN move to next annotation and repeat.                  │
│                                                             │
│   ─────────────────────────────────────────────────────     │
│                                                             │
│   DO NOT: Insert all markers, then append all definitions    │
│   RIGHT: Insert marker → append definition → next marker    │
│                                                             │
└─────────────────────────────────────────────────────────────┘

CORRECT WORKFLOW

flowchart TD
    A[Copy original to annotated file] --> B[Identify first annotation location]
    B --> C[Insert Single marker in annotated file]
    C --> D[Append Single definition to footnotes file]
    D --> E{More annotations?}
    E -->|Yes| F[Identify next annotation location]
    F --> B
    E -->|No| G[Done]

FOOTNOTE DEFINITION FORMAT

Single-Line Footnote

[^marker-id]: Short definition on the same line.

---

Multi-Line Footnote (4-SPACE INDENT)

For multi-line definitions, put the marker on its own line, then indent all content with 4 spaces:

[^marker-id]:
    First line of the definition starts here with 4-space indent.
    
    Additional paragraphs also indented 4 spaces.
    
    **Markdown formatting** works normally within the indented block.
    
    - Lists work too
    - Just keep the 4-space indent

---

Read the full file on GitHub · 283 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. yesterday First seen · 283 lines · 58 tokens per session scan A 30b7cdcbfe75

Subscribe to this mod's changes

source-command-annotate is a skill published in the GitHub repository noizu-labs-ml/NoizuPromptLingo (13 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 1,662 once invoked, about $0.0003 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-09-04.

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

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 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

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens