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-make-fluentgit 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-make-fluent)<a href="https://agentmods.dev/skills/kirodotdev/kirocrew/papyrus-make-fluent"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/papyrus-make-fluent/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-make-fluent"><img src="https://agentmods.dev/badge/skills/kirodotdev/kirocrew/papyrus-make-fluent.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.00071 | $0.00477 |
| Opus 5 | $0.00036 | $0.00238 |
| Sonnet 5 | $0.00014 | $0.00095 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
papyrus-make-fluent 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 3d 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.
What it actually says
Make Fluent
Polish mode: improve HOW it reads, never WHAT it says or WHERE it sits. Follow
papyrus-writing for conduct, the clarity principles (Gopen & Swan), and the
house style; produce every change as a tracked suggestion via
papyrus-latex-suggestions (paired with a comment giving the reason) — never
overwrite silently. This skill adds only what is specific to polishing: the scope
fence and chameleon-mode.
Scope fence
- MAY change: grammar, spelling, agreement, articles, tense; awkward or wordy phrasing → tighter and clearer (topic/stress position, subject close to verb, old→new flow); hedging and redundancy.
- MUST NOT change: the structure — don't move, merge, split, add, or delete sentences/paragraphs (flag it instead); the meaning — never a claim, number, result, definition, or citation; the author's voice — match their terminology, notation, macros, and bib keys, don't flatten to generic prose; the layout — don't rewrap paragraphs you weren't asked to touch.
Chameleon mode
Before editing, read a few passages the author has already written fluently to learn their register and level of English, then match it — don't homogenize a distinctive or non-native voice into generic prose. Read enough surrounding text to keep terminology consistent, and keep every edit sentence-local and minimal (one suggestion per issue).
After polishing
Run the ripple / global-consistency check from papyrus-writing §7 — a local
rewording can desync the abstract, captions, notation, or cross-references. FLAG
anything affected and offer to propagate; never propagate silently.
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.
- 3d ago First seen · 37 lines · 71 tokens per session scan A e02ff41d17fb
papyrus-make-fluent is a skill published in the GitHub repository kirodotdev/KiroCrew (3,860 stars, last pushed today), licensed Apache-2.0. It adds 71 tokens to every session and 477 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…