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-diagnose-compilationgit 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-diagnose-compilation)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/papyrus-diagnose-compilation"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/papyrus-diagnose-compilation/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-diagnose-compilation"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/papyrus-diagnose-compilation.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.00060 | $0.00725 |
| Opus 5 | $0.00030 | $0.00362 |
| Sonnet 5 | $0.00012 | $0.00145 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
papyrus-diagnose-compilation 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnose LaTeX Compilation
Turn a failed build into a located, classified, minimally-fixed error. Never mass-rewrite the source to "make it compile" — find the one thing that broke.
In Papyrus the app owns compilation (Cmd+S / Ctrl+S), so you normally read the error from the app's clickable diagnostics list rather than compiling yourself. The steps below apply whether you are reading that list or, outside the app, running the compiler directly.
Step 1 — Read the FIRST real error
Work from the first error, not the last: LaTeX errors cascade, and the tail of
the log is usually damage from the head. In the app, the diagnostics list is
already ordered — start at the top. If you do have a raw log, the first
file:line: message (or ! …) line is the one to fix.
-file-line-error makes a compiler print file:line: message. If citations/refs
are wrong (not the compile itself), the full cycle is pdflatex → bibtex/biber
→ pdflatex → pdflatex; Tectonic runs that cycle itself.
Step 2 — Classify and fix at the source line
Common cause → fix:
- Unescaped special char (
_ % & # $in text) → escape it (\_,\%, …). - Unbalanced brace / missing
}or\end{env}→ match the environment. Undefined control sequence→ missing\usepackage, or a typo'd/renamed macro.File 'x.sty' not found→ package not installed in this TeX distribution; prefer a package the document already loads over telling the author to install one.File not found(graphic/\input) → wrong path or extension; confirm the file exists.Missing $ inserted→ math symbol (_,^,\alpha) used outside math mode; wrap in$…$or an equation env.Missing \begin{document}→ a stray character before the preamble ended.- Bib:
Citation 'key' undefined/ stale.bbl→ add the entry to the.bib(don't remove the\cite), then run bibtex/biber and two more pdflatex passes. There's no line here to end→ a\\on an otherwise-empty line.Overfull \hbox,Underfull, mostWarning:lines are WARNINGS, not errors — do NOT "fix" them by hacking spacing (seepapyrus-writing: never hack margins).
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 · 51 lines · 60 tokens per session scan A 4ea3b4d5acde
papyrus-diagnose-compilation is a skill published in the GitHub repository kirodotdev/KiroCrew (3,823 stars, last pushed today), licensed Apache-2.0. It adds 60 tokens to every session and 725 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-09.
Other skills, from other repositories
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.
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…
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
document-converter
Convert documents bidirectionally via the pi-doc-engine facade: ingest PDF/DOCX/PPTX/XLSX to provenance-stamped Markdown (with OCR), and produce templated DOCX/PDF from Markdown with diagrams, TOC and round-trip merge. Use on "convert this PDF to markdown", "ingest these docs into kb", "make a DOCX from markdown with…
add-pdf-reader
Add PDF reading to ClaudeClaw agents. Extracts text from PDFs via pdftotext CLI. Handles WhatsApp attachments, URLs, and local files.
Use this skill whenever the user mentions a PDF file or asks to produce/edit one. For read-only tasks such as reading, summarizing, extracting plain text, or answering questions from a PDF, follow this skill's read-only routing rules: use the built-in Read tool first, do not write code or scripts, and prefer…