find-annotations

find-annotations is a skill for Claude Code, Codex from Rezenders/scientific_writing_agent. It costs 27 tokens per session (486 once invoked), scanned A, original, Apache-2.0.

A manuscript-scanning skill for finding open inline notes in LaTeX files. LaTeX is a text-based system commonly used to write technical papers.

In plain words
What is it for?
Use it to search `.tex` files for commands such as `\todo`, `\revise`, and `\red`, then report each note with its file, line number, type, and content.
Why use it?
It gives writers one inventory of unfinished tasks, revision notes, warnings, and author comments before editing or submitting a paper.

Skill for Claude CodeCodex

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

Good fit Use it to search .tex files for commands such as \todo, \revise, and \red, then report each note with its file, line number, type, and content.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rezenders/scientific_writing_agent/find-annotations
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 Rezenders/scientific_writing_agent --skill find-annotations
Clone the repo
git clone --depth 1 https://github.com/Rezenders/scientific_writing_agent

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 find-annotations

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/rezenders/scientific_writing_agent/find-annotations"><img src="https://agentmods.dev/badge/skills/rezenders/scientific_writing_agent/find-annotations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 486 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.00027 $0.00486
Opus 5.5 $0.00011 $0.00194
Sonnet 5.5 $0.00005 $0.00097
Haiku 4.5 $0.00003 $0.00049

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

Security

Grade A, and why

find-annotations 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 1mo 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/find-annotations/SKILL.md · 53 lines

What it actually says

Find Annotations

Scan manuscript .tex files for open inline annotations and report them grouped by annotation type.

Annotation Commands In This Repository

Customize this list from AGENTS.md, .agents/context/terminology.md, or the macro definitions in the manuscript project. Common examples:

  • \todo{...}
  • <AUTHOR_COMMENT_MACRO>{...}
  • \red{...}
  • \hide{...}

Workflow

  1. Run rg -n across *.tex files in <PROJECT_ROOT>.
  2. Search for each annotation command above.
  3. Skip config/macros.tex, which defines commands rather than using them.
  4. Filter out matches from commented-out TeX lines whose content begins with optional whitespace followed by %.
  5. Flag matches under old/ separately because they are archival and are not part of the active manuscript unless the user explicitly says otherwise.
  6. Group results by annotation type and report file, line, and extracted content.

Example command:

cd <PROJECT_ROOT>
rg -n --glob '*.tex' --glob '!<MACROS_OR_CONFIG_FILE>' \
  '\\todo\{|<AUTHOR_COMMENT_MACRO>\{|\\red\{|\\hide\{' \
  | rg -v '^[^:]+:[0-9]+:\s*%'

Reporting Requirements

  • Group \todo, \red, and \hide separately.
  • Group author comment macros together, with per-author subsections when useful.
  • Include the file path and line number for each match.
  • Extract and summarize the annotation content inside {...} when practical.
  • Report totals for active-manuscript annotations and affected files.
  • Report old/ matches separately and treat them as non-blocking by default.

If no annotations are found, report: No open annotations - manuscript is clean.

Notes

  • \red{} is blocking when it appears in active manuscript files because it appears in the rendered manuscript.
  • \hide{} in active manuscript files may not appear in the PDF, but it still requires author review.
  • Treat annotation macros as manuscript content to review, not inert comments.
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. 1mo ago Changed · -16 lines · -8 tokens per session d4a5199662ea
  2. 2mo ago First seen · 69 lines · 35 tokens per session scan A f86622639e8f

Subscribe to this mod's changes

find-annotations is a skill published in the GitHub repository Rezenders/scientific_writing_agent (14 stars, last pushed 17d ago), licensed Apache-2.0. It adds 27 tokens to every session and 486 once invoked, about $0.0001 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-08-30.

Related

find-annotations compared with skills from other repositories

find-annotations next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
find-annotationsRezenders/scientific_writing_agentSkill1417d agoApache-2.0A27Claude Code, Codex
orbit-notionnexu-io/open-designSkill106kyesterdayApache-2.0A117Claude Code, Codex
instrument-data-to-allotropeanthropics/knowledge-work-pluginsSkill35k2d agoApache-2.0A123Claude Code
apify-youtube-transcript-scrapersickn33/agentic-awesome-skillsSkill49kyesterdayMITA48Claude Code
legal-holdanthropics/claude-for-legalSkill9.9k3d agoApache-2.0A68Claude Code
ppt-reviewOrkas-AI/OrkasSkill9.0kyesterdayMITA2Claude Code, Codex
feishuHmbown/CodeWhaleSkill41k5d agoMITA33Claude Code, Codex