papyrus-latex-suggestions

papyrus-latex-suggestions is a skill for Claude Code, Codex from kirodotdev/KiroCrew. It costs 69 tokens per session (1,229 once invoked), scanned A, original, Apache-2.0.

A LaTeX suggestion layer for showing proposed text changes as tracked edits. Authors can see the original and replacement text in the PDF and accept or reject the proposal.

In plain words
What is it for?
Use it to propose concrete replacements in a .tex document, such as grammar or wording edits, while recording why each change was suggested.
Why use it?
It keeps the original document visible and avoids silently overwriting an author's wording.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to propose concrete replacements in a .tex document, such as grammar or wording edits, while recording why each change was suggested.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kirodotdev/kirocrew/papyrus-latex-suggestions
About the project

Kiro Crew is a persistent development workspace where agents continue multi-step software work across sessions, schedules, and connected interfaces. Developers use it locally or remotely through a desktop app, web dashboard, CLI, Slack, or Discord, with unattended tasks and recurring jobs. The catalogue contains skills and instructions for working with this workspace.

kirodotdev/KiroCrew · 4,571 stars · on GitHub · kiro.dev

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 kirodotdev/KiroCrew --skill papyrus-latex-suggestions
Clone the repo
git clone --depth 1 https://github.com/kirodotdev/KiroCrew

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 papyrus-latex-suggestions

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/papyrus-latex-suggestions"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/papyrus-latex-suggestions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,229 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.00069 $0.01229
Opus 5.5 $0.00028 $0.00492
Sonnet 5.5 $0.00014 $0.00246
Haiku 4.5 $0.00007 $0.00123

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

Security

Grade A, and why

papyrus-latex-suggestions 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 4d 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.

src/kiro_crew/builtin_skills/papyrus-latex-suggestions/SKILL.md · 89 lines

How it starts

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

LaTeX Suggestions (inline tracked edits)

Propose concrete replacement text the author sees as struck-through old + colored new, and can accept or reject — the original stays visible until they decide. Never silently overwrite. It renders as normal typeset text (via ulem), so it shows in any PDF viewer including the Papyrus preview — no package to install, no PDF annotations. See papyrus-writing for behaviour. Pair every suggestion with a papyrus-latex-comments \aicomment saying WHY.

Step 1 — Setup (idempotent)

ulem and xcolor ship with TeX Live — no tlmgr install. If the document has no suggestion preamble yet, inject this once at the end of the preamble, after all existing \usepackage lines (never duplicate it if it is already there):

% Load ulem/xcolor ONLY if the document hasn't already loaded them (avoids an option clash).
\makeatletter
\@ifpackageloaded{ulem}{}{\usepackage[normalem]{ulem}}   % \sout (strike) + \uline (underline); normalem keeps \emph italic
\@ifpackageloaded{xcolor}{}{\usepackage{xcolor}}         % \color for the strike/insert colors
\makeatother
% ==== Papyrus suggestion layer ====
% Flip to \showeditsfalse to render the FINAL text only (visually accepts every change).
\newif\ifshowedits \showeditstrue
\newcommand{\aisuggest}[3][]{\ifshowedits{\color{red}\sout{#2}}\,{\color{blue}#3}\else#3\fi}
\newcommand{\txadd}[2][]{\ifshowedits{\color{blue}\uline{#2}}\else#2\fi}
\newcommand{\txremove}[2][]{\ifshowedits{\color{red}\sout{#2}}\else\fi}
% =====================================================================================

The optional [...] first argument carries metadata (author=papyrus, id=R12, status=pending): it documents the change, but it is not rendered.

This preamble does NOT define \aicomment. Every suggestion is paired with one (Step 2), so also make sure the papyrus-latex-comments preamble is present — inject it the same way if it is missing — or the compile fails with Undefined control sequence \aicomment.

Read the full file on GitHub · 89 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. 4d ago Changed · +1 lines c6eaa07da717
  2. 17d ago Changed · +5 lines 4e3b0dd5b5c6
  3. 1mo ago Changed · -8 tokens per session c0c25e07c6f7
  4. 1mo ago First seen · 83 lines · 77 tokens per session scan A f4ef86367c90

Subscribe to this mod's changes

papyrus-latex-suggestions is a skill published in the GitHub repository kirodotdev/KiroCrew (4,571 stars, last pushed today), licensed Apache-2.0. It adds 69 tokens to every session and 1,229 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-09.