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 kubiyabot/skill --skill simple-skillgit clone --depth 1 https://github.com/kubiyabot/skillWrote 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/kubiyabot/skill/simple-skill)<a href="https://agentmods.dev/skills/kubiyabot/skill/simple-skill"><img src="https://agentmods.dev/badge/skills/kubiyabot/skill/simple-skill/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/kubiyabot/skill/simple-skill"><img src="https://agentmods.dev/badge/skills/kubiyabot/skill/simple-skill.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.02801 |
| Opus 5.5 | $0.00006 | $0.01120 |
| Sonnet 5.5 | $0.00003 | $0.00560 |
| Haiku 4.5 | $0.00002 | $0.00280 |
Grade A, and why
simple-skill 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.
How it starts
The opening of the file, as written. The whole thing — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simple Skill
A minimal example demonstrating how easy it is to create skills with Skill Engine. This skill showcases the basic patterns for defining tools, handling parameters, and returning results - perfect for learning or as a template for new skills.
Overview
This skill requires no build steps - just write JavaScript and run! The runtime automatically compiles to WASM on first run and caches the result for fast subsequent executions.
When to Use This Skill
Use this skill to:
- Learn the basics of Skill Engine development
- Test skill execution and parameter handling
- Understand the skill.js file structure
- Use as a template for creating new skills
Use this skill as a reference when:
- Starting a new skill from scratch
- Understanding parameter types and validation
- Learning error handling patterns
- Setting up tool metadata
Features
- No build steps required - Just write JavaScript and run
- Auto-compilation - Runtime compiles to WASM on first run (~2-3 seconds) and caches
- Fast execution - Subsequent runs use cached WASM (<100ms startup)
- Auto-recompile - Modifications to skill.js trigger automatic recompilation
- Simple API - Export functions matching the skill interface
- Type-safe - Tool definitions provide schema for arguments
Tools
hello
Greet someone with a friendly message.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| name | string | Yes | - | Name of the person to greet |
| greeting | string | No | Hello | Custom greeting message |
Example:
# Basic greeting
skill run simple-skill hello name=World
# Output: Hello, World! 👋
# Custom greeting
skill run simple-skill hello name=Alice greeting="Hi"
# Output: Hi, Alice! 👋
# Direct path execution
skill run ./examples/wasm-skills/simple-skill hello name=Bob
echo
Echo back the provided message, optionally repeating it multiple times.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| message | string | Yes | - | Message to echo back |
| repeat | number | No | 1 | Number of times to repeat the message |
What ships with it
9 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.
- 1mo ago First seen · 450 lines · 15 tokens per session scan A 7cf1509696c7
simple-skill is a skill published in the GitHub repository kubiyabot/skill (19 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 2,801 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-09-03.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.