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 serejaris/kimi-skills --skill geo-magazine-slides-cngit clone --depth 1 https://github.com/serejaris/kimi-skillsWrote 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/serejaris/kimi-skills/geo-magazine-slides-cn)<a href="https://agentmods.dev/skills/serejaris/kimi-skills/geo-magazine-slides-cn"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/geo-magazine-slides-cn/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/serejaris/kimi-skills/geo-magazine-slides-cn"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/geo-magazine-slides-cn.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.00095 | $0.02348 |
| Opus 5 | $0.00048 | $0.01174 |
| Sonnet 5 | $0.00019 | $0.00470 |
| Haiku 4.5 | $0.00010 | $0.00235 |
Grade A, and why
geo-magazine-slides-cn 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- geo-magazine-slides — 92% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Geographic Magazine Presentation
Create high-end editorial presentation decks modeled after luxury geographic magazines. The style combines large-format photography placeholders, clean serif/sans-serif typography, a bold red-and-gray color system, and structured data visualizations.
Reference Source
- Type: Uploaded artifact (PPTX)
- Reference artifact type: PPTX
- Effective Reference File Type: PPTX
- Fonts extracted from reference: Oranienbaum (serif headings), Liter (sans-serif body)
Supported Outputs
- PPTX (default and primary)
Default Output Selection
- If user explicitly requests a format, use that format
- Otherwise, default to PPTX
Workflow
1. Gather Content Requirements
Collect from the user:
- Topic: What geographic collection is being presented (city, region, properties, landmarks)
- Items: The individual items/locations to feature (target ~20 items for full structure)
- Data points: Key metrics per item (prices, sizes, dates, ratings — varies by domain)
- Visual assets: Available photos or confirm use of dark placeholder rectangles
- Narrative flow: Preferred grouping by region, category, or ranking
2. Read the Style and Structure Contracts
Before creating any slides, read both reference files to internalize the visual language:
references/style_contract.md— Full color palette (exact hex), typography system, layout rules with measurements, image/chart treatment, and slide-specific layout patternsreferences/structure_contract.md— Exact 15-slide sequence, section hierarchy, content block patterns, and mandatory elements checklist
3. Plan the Slide Deck
Map content to the required 15-slide sequence (see structure contract). For each slide:
- Determine slide type (cover, overview, section divider, detail, chart, theme, closing)
- Assign text content and hierarchy levels
- Plan image placeholder positions (dark rectangles, NEVER external image downloads)
- Prepare data for charts (horizontal bar chart on slide 5, vertical bar chart on slide 9)
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.
- 9d ago First seen · 172 lines · 95 tokens per session scan A e337e4b33c9e
geo-magazine-slides-cn is a skill published in the GitHub repository serejaris/kimi-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 95 tokens to every session and 2,348 once invoked, about $0.0005 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-03.
Other skills, from other repositories
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build landing pages, websites, dashboards, web components, or any frontend UI. Generates creative, polished code that avoids generic AI aesthetics.
prototype
Build a self-contained local prototype at .turbo/prototypes/ .html, drive it, and hand it to the user to settle unknowns that prose cannot answer. Use when the user asks to "prototype this", "build a prototype", "mock this up", "show me what it would look like", "let me try the interaction first", or when a decision…
user-experience
Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and…
slop-eval
Objectively evaluate a UI/web design against the pols.dev anti-slop design law: detect catalogued slop tells with cited evidence, score 8 weighted axes (color, type, components, layout, motion, execution, signature, cohesion), and emit a Slop Report with a 0–100 Slop Index and grade. Use when the user asks to…
revenue-centric-design
Revenue-Centric Design (RCD) — evidence-backed principles for making a SaaS or startup product convert, retain, and monetize. Use when the user works on a landing page or CRO ("my page isn't converting"), onboarding/activation ("users sign up but don't stick"), churn/retention ("customers keep canceling")…