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.
git clone --depth 1 https://github.com/hletrd/kiwi-paperWrote 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/rules/hletrd/kiwi-paper/cursor)<a href="https://agentmods.dev/rules/hletrd/kiwi-paper/cursor"><img src="https://agentmods.dev/badge/rules/hletrd/kiwi-paper/cursor/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/rules/hletrd/kiwi-paper/cursor"><img src="https://agentmods.dev/badge/rules/hletrd/kiwi-paper/cursor.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.00015 | $0.00313 |
| Opus 5.5 | $0.00006 | $0.00125 |
| Sonnet 5.5 | $0.00003 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
CURSOR 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 1mo 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
kiwi-paper
기술 문서를 나무위키 스타일로 변환하는 도구입니다.
사용자가 kiwi-paper 변환을 요청하면 SKILL.md 파일의 지시사항을 따르세요.
핵심 지시사항은 이 프로젝트의 SKILL.md 파일에 있습니다. 반드시 읽고 4단계 파이프라인을 따르세요.
4단계 파이프라인
- 초안 작성 -- 입력 문서를 나무위키 스타일 마크다운으로 변환
- 다듬기 -- 구조, 유머, 링크, 이미지 보강
- 휴머나이즈 -- AI 티 제거, 자연스러운 한국어
- HTML 렌더링 --
node <kiwi-paper-path>/renderer/src/render.mjs -i <file> -o <dir>
핵심 규칙
- 취소선(~~) 섹션당 3-5개, 전체 15개 이상
- 각주 8개 이상 (출처 6 : 유머 4 비율)
- 여담 섹션 5개 항목 이상
- 이미지: 원본의 모든 Figure/Table 포함
- 12종 문서 유형 지원 (논문, 스펙, API 문서, 매뉴얼, 뉴스 등)
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.
- 1mo ago First seen · 28 lines · 15 tokens per session scan A dde6b9227b36
CURSOR is a cursor rule published in the GitHub repository hletrd/kiwi-paper (15 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 313 once invoked, about $0.0001 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-08-30.
Other cursor rules, from other repositories
ilana
Ìlànà software engineering process. Load for requirements, elicitation, SRS, traceability, architecture, interface design, coding standards, code review, testing at any level, test planning, defect tracking, configuration management, Git branching, change control, build and release, CI/CD, quality assurance, reviews…
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).