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.
curl -O https://raw.githubusercontent.com/noizu-labs-ml/NoizuPromptLingo/main/.claude/commands/annotate.mdgit clone --depth 1 https://github.com/noizu-labs-ml/NoizuPromptLingoWrote 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/noizu-labs-ml/noizupromptlingo/annotate)<a href="https://agentmods.dev/commands/noizu-labs-ml/noizupromptlingo/annotate"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/annotate/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/commands/noizu-labs-ml/noizupromptlingo/annotate"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/annotate.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.00055 | $0.01628 |
| Opus 5 | $0.00028 | $0.00814 |
| Sonnet 5 | $0.00011 | $0.00326 |
| Haiku 4.5 | $0.00006 | $0.00163 |
Grade A, and why
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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- annotate — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
---
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.
- 5d ago First seen · 277 lines · 55 tokens per session scan A 0e7e36522032
annotate is a command published in the GitHub repository noizu-labs-ml/NoizuPromptLingo (13 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 1,628 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.