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/wolfenazz/yzpzcode/kami-landingnpx skills add wolfenazz/YzPzCode --skill kami-landinggit clone --depth 1 https://github.com/wolfenazz/YzPzCodeWrote 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/wolfenazz/yzpzcode/kami-landing)<a href="https://agentmods.dev/skills/wolfenazz/yzpzcode/kami-landing"><img src="https://agentmods.dev/badge/skills/wolfenazz/yzpzcode/kami-landing.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 | $0.00081 | $0.02529 |
| Opus 5 | $0.00041 | $0.01264 |
| Sonnet 5 | $0.00016 | $0.00506 |
| Haiku 4.5 | $0.00008 | $0.00253 |
Grade A, and why
kami-landing 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.
This is a copy
95% identical to kami-landing — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kami-landing
Produce a single-page document in the kami (紙 / 纸) design system. The aesthetic borrows from editorial print, technical white papers, and old typewritten correspondence — the goal is good content on good paper, not modern app UI.
Design system source of truth:
design-systems/kami/DESIGN.md. Read it before shipping. Tokens, type rules, the "ten invariants", and forbidden colors all live there.
What you get
A single self-contained HTML file with:
- Warm parchment canvas (
#f5f4ed) — never#ffffff. - Single chromatic accent — ink-blue (
#1B365D), used on the section number, the headline accent word, the left rule of the manifesto, and the metric values. Anywhere else, ink-blue must cover ≤ 5% of the document surface area. - Serif at one weight (500) for hierarchy — Charter (EN),
TsangerJinKai02 / Source Han Serif (CN), or YuMincho (JA),
selected by the
languageparameter. No italic anywhere. - Tight print rhythm — line-heights 1.10–1.55, letter-spacing per language (0 for EN, 0.35px for CN, 0.02em for JA).
- Numeric stacks set in
font-variant-numeric: tabular-numsso metric columns and pagination digits sit cleanly aligned. - Depth via 1px rings + whisper shadows (
0 4px 24px rgba(0,0,0,0.05)). No hard drop shadows, no neumorphism, no backdrop-filter blurs. - Tag fills as solid hex (e.g.
#E4ECF5), neverrgba()— print renderers double-paint alpha tags. - Responsive at 1280 / 980 / 768 / 560.
Page structure
1. Eyebrow row — locale switcher · edition · version (12px sans uppercase)
2. Hero — display headline (96–106px serif 500), tagline (21px),
three hero-token chips (paper-tinted)
3. Manifesto — pull paragraph in serif 400, 20px, 1.65 LH, with
ink-blue left-rule and signature footer
4. Metrics row — 3-6 cells: value (24px serif 500 ink-blue, tabular-nums),
label (12px serif 500 olive)
5. Chapters — numbered (`01`, `02`, …) ink-blue serif 500 14px,
section title 28-32px, body 14-15px
6. Footer — kicker word (mega serif 500), license · year · contact,
three-column site index in 12px serif 500
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 234 lines · 81 tokens per session scan A f50310e16eb5
kami-landing is a skill published in the GitHub repository wolfenazz/YzPzCode (13 stars, last pushed yesterday), licensed Apache-2.0. It adds 81 tokens to every session and 2,529 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to kami-landing, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
sif-to-csv
Parse a SIF (Standard Interchange Format) input into a readable preview and optionally append canonical product rows to the project's CSV library. Use when asked to convert or inspect SIF dealer data. For the reverse direction use /as:csv-to-sif.
latex-polish
Inspect a cleanly compiling LaTeX document for source pathologies and rendered visual defects by linting and viewing selected PDF pages. Use when compilation succeeds but title pages, floats, tables, figures, or layout still need publication-quality review. Not for basic compilation health; use $latex-health-check.
beautiful-pdfs
Build polished PDF documents by composing semantic HTML/CSS and rendering HTML to PDF.
bib-coverage
Compare a project .bib against a Paperpile project/topic folder to find uncited papers or unfiled entries. Use when the user asks to compare a project .bib against a Paperpile project/topic folder to find uncited papers or unfiled entries.
meeting-minutes-taker
Transforms raw meeting transcripts into high-fidelity, structured meeting minutes with iterative review for completeness. This skill should be used when (1) a meeting transcript is provided and meeting minutes, notes, or summaries are requested, (2) multiple versions of meeting minutes need to be merged without losing…
Use this skill when the user asks to inspect or summarize PDF documents.