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.
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.
npx skills add kirodotdev/KiroCrew --skill papyrus-latex-commentsgit clone --depth 1 https://github.com/kirodotdev/KiroCrewWrote 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/skills/kirodotdev/kirocrew/papyrus-latex-comments)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/papyrus-latex-comments"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/papyrus-latex-comments/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/skills/kirodotdev/kirocrew/papyrus-latex-comments"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/papyrus-latex-comments.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.00080 | $0.00853 |
| Opus 5 | $0.00040 | $0.00426 |
| Sonnet 5 | $0.00016 | $0.00171 |
| Haiku 4.5 | $0.00008 | $0.00085 |
Grade A, and why
papyrus-latex-comments 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LaTeX Comments
Add a visible, attributable, removable layer of NOTES to a LaTeX document —
remarks ABOUT the text, never a rewrite of it. Insert a macro call next to the
relevant text. See papyrus-writing for the behaviour rules and the comment
taxonomy. To propose concrete replacement text (accept/reject), use
papyrus-latex-suggestions.
Step 1 — Setup (idempotent)
kpsewhich todonotes.sty # non-empty = installed (ships with TeX Live — usually no install)
If the document has no comment preamble yet, inject this once at the end of the preamble, after all existing \usepackage lines (never duplicate it if it is already there):
% ==== Papyrus comment layer — safe to leave in; flip to hide ====
% Load todonotes ONLY if the document hasn't already loaded it (avoids an option clash).
\makeatletter
\@ifpackageloaded{todonotes}{}{\usepackage[textsize=scriptsize]{todonotes}}
\makeatother
\newcommand{\aicomment}[1]{\todo[color=cyan!25,bordercolor=cyan]{\textbf{AI:} #1}} % margin note
% FINAL BUILD: hide every note by adding the `disable` option to todonotes
% (wherever it is loaded): \usepackage[disable]{todonotes}.
% ================================================================
Margin space is tight, so textsize=scriptsize keeps notes readable in a
one-column margin. Comments live in the margin only — a note must never
change the paper's length or reflow the text. In a two-column or narrow-margin
paper, keep each note short rather than pushing it into the text flow.
Step 2 — Insert comments
Add a macro call next to the relevant text. Do NOT rewrite the prose. Tag every
note with the taxonomy ([claim] [cite] [clarity] [structure] [contribution] [rigor] [style] [typo]).
The method is fast.\aicomment{[claim] by how much? add a number + CI}
This paragraph reads like Related Work.\aicomment{[structure] consider moving it there}
We imitate the baseline.\aicomment{[clarity] ``imitate'' is imprecise — say exactly what you did to the baseline}
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.
- yesterday First seen · 74 lines · 80 tokens per session scan A 655daa5cff22
papyrus-latex-comments is a skill published in the GitHub repository kirodotdev/KiroCrew (3,823 stars, last pushed today), licensed Apache-2.0. It adds 80 tokens to every session and 853 once invoked, about $0.0004 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-09.
Other skills, from other repositories
ppt-generation
Generate PPTX presentations from slide plan + content.
data-analysis
Analyze Excel/CSV files with DuckDB SQL via bash.
document-processor
Guidance for processing documents, extracting content, and transforming structured information. Use when the user asks to process, parse, extract, or transform document content such as PDFs, Word files, or spreadsheets.
attendance-signin-sheet
A spreadsheet generator for printable attendance or meeting sign-in sheets. It turns a list of names into rows with columns such as signatures, dates, departments, or employee IDs.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and…
cost-efficiency-analyzer
Analyzes cost structure, cost efficiency, and expense management from P&L data. Use when the user asks about costs, expenses, COGS, operating expenses, cost ratios, cost control, spending efficiency, margin compression from cost side, or wants to understand where money is going. Also use for "are we spending too…