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 agentmods add skills/kirodotdev/kirocrew/papyrus-writingnpx skills add kirodotdev/KiroCrew --skill papyrus-writinggit 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-writing)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/papyrus-writing"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/papyrus-writing.svg" alt="Measured on agentmods" 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.01393 |
| Opus 5 | $0.00028 | $0.00696 |
| Sonnet 5 | $0.00011 | $0.00279 |
| Haiku 4.5 | $0.00006 | $0.00139 |
Grade A, and why
papyrus-writing 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LaTeX paper writing
You are editing a real manuscript that someone will submit. Two rules dominate everything else:
- Preserve the author's voice. Suggest, don't rewrite. When a sentence is merely different-not-better, leave it alone.
- Read before you edit. The user may have changed the file since your last read, and in the Papyrus app they are editing it live in the other pane. Read the file, then make a minimal, surgical edit.
Show the exact LaTeX you changed. A diff of two lines is more useful than a paragraph describing the change.
Papyrus app specifics
When the user is working in the Papyrus app, the paper lives under the app's data directory:
<KiroCrew data home>/apps/papyrus/data/projects/<project>/
The KiroCrew data home is ~/.kiro/crew unless KIROCREW_HOME is set. Each
project has a main .tex file (usually main.tex), typically a
references.bib, and often a sections/ or figures/ subfolder.
- Which project you are in is in the chat session title:
papyrus-<project>. - Read and edit the
.texfiles with your normal file tools. Do NOT try to compile by shelling out topdflatex— the app owns compilation, and it deliberately runs the compiler with shell escape DISABLED. After you edit, tell the user to press Cmd+S (Ctrl+S on Linux) and the PDF pane refreshes. - Compilation errors are surfaced in the app as a clickable list. If the user
pastes one, the line number refers to the file named in the message, which is
not always the main document (an error inside
\input{sections/intro}reportssections/intro.tex).
Fixing compilation errors
Work from the FIRST error, not the last: LaTeX errors cascade, and the tail of the log is usually damage from the head.
| Message | Usual cause |
|---|---|
Undefined control sequence |
A typo'd macro, or a missing \usepackage |
File 'x.sty' not found |
Package not installed in this TeX distribution — prefer a package the document already loads over telling the user to install one |
Missing $ inserted |
Math symbol (_, ^, \alpha) used outside math mode |
Missing \begin{document} |
Something before the preamble ended, often a stray character |
Citation 'key' undefined |
Key absent from the .bib, or the bibliography needs another pass — add the entry rather than removing the \cite |
There's no line here to end |
A \\ on an otherwise-empty line |
Overfull \hbox |
Not an error. A line ran into the margin; fix it only if the user asks |
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.
- 6d ago First seen · 134 lines · 55 tokens per session scan A bd00f17df13c
papyrus-writing is a skill published in the GitHub repository kirodotdev/KiroCrew (3,661 stars, last pushed today), licensed Apache-2.0. It adds 55 tokens to every session and 1,393 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-08-30.
Other skills, from other repositories
systematic-literature-review
Systematic literature review across multiple arXiv papers.
arxiv
Search arXiv papers by keyword, author, category, or ID.
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…
multi-quarter-trend-analysis
Analyzes financial trends across multiple quarters by comparing P&L metrics over time. Use when the user wants to see trends, patterns, trajectories, or directional movement across 3 or more quarters. Also use for "how are we trending", "show me the trend", "track performance over time", "quarter over quarter…
sector-rotation
Identify which market sectors to overweight or underweight based on current macro conditions and sector performance data.
trend-analysis
Analyze price and volume trends for one or more stocks to determine momentum direction and key technical levels.