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 iammohdzaki/kmp-skills --skill _templategit clone --depth 1 https://github.com/iammohdzaki/kmp-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/iammohdzaki/kmp-skills/_template)<a href="https://agentmods.dev/skills/iammohdzaki/kmp-skills/_template"><img src="https://agentmods.dev/badge/skills/iammohdzaki/kmp-skills/_template/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/iammohdzaki/kmp-skills/_template"><img src="https://agentmods.dev/badge/skills/iammohdzaki/kmp-skills/_template.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.00022 | $0.00327 |
| Opus 5 | $0.00011 | $0.00163 |
| Sonnet 5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
your-skill-name 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 10d 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
Skill Title
One paragraph summary of what this skill does and when the agent should use it.
When to Use This Skill
- Bullet points describing the scenarios where this skill applies.
- Be specific so the agent knows when to activate it.
Pre-flight Questions (if interactive)
If this skill requires user input before generating output, list the questions here. The agent MUST ask ALL of these before writing any code.
- Question one?
- Question two?
Core Concepts
Explain the main concepts, patterns, or guidelines this skill covers.
Concept 1
Details...
Concept 2
Details...
Step-by-Step Instructions
Numbered steps the agent should follow.
- Step one
- Step two
- Step three
Reference Files
| File | Description |
|---|---|
| references/example.md | Describe what this reference covers |
Rules & Constraints
- Rule 1: Something the agent must always do.
- Rule 2: Something the agent must never do.
- Rule 3: A constraint or guardrail.
Official Docs
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.
- 10d ago First seen · 81 lines · 22 tokens per session scan A f0759b3a2a66
your-skill-name is a skill published in the GitHub repository iammohdzaki/kmp-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 327 once invoked, about $0.0001 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-31.
Other skills, from other repositories
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
playwright-skill
Battle-tested Playwright patterns for writing, debugging, and scaling reliable test suites. Use when you need guidance for E2E, API, component, visual, accessibility, or security testing, plus CI/CD, CLI automation, page objects, and migration from Cypress or Selenium. TypeScript and JavaScript.
playwright-core
Battle-tested Playwright patterns for writing and debugging reliable E2E, API, component, visual, accessibility, and security tests. Use when you need locator strategy, assertions, fixtures, network mocking, auth flows, trace debugging, or framework recipes for React, Next.js, Vue, and Angular. TypeScript and…
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
playwright-migration
Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.
playwright-pom
Page Object Model patterns for Playwright — when to use POM, how to structure page objects, and when fixtures or helpers are a better fit.