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 bug-ops/zeph --skill skill-creatorgit clone --depth 1 https://github.com/bug-ops/zephWrote 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/bug-ops/zeph/skill-creator)<a href="https://agentmods.dev/skills/bug-ops/zeph/skill-creator"><img src="https://agentmods.dev/badge/skills/bug-ops/zeph/skill-creator/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/bug-ops/zeph/skill-creator"><img src="https://agentmods.dev/badge/skills/bug-ops/zeph/skill-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 7 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- high Rogue Agent · line 63 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- high Anti-Refusal · line 125 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00075 | $0.00911 |
| Opus 5.5 | $0.00030 | $0.00364 |
| Sonnet 5.5 | $0.00015 | $0.00182 |
| Haiku 4.5 | $0.00007 | $0.00091 |
Grade B, and why
skill-creator scanned grade B with 1 finding 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
4. **Security first** — never include secrets, credentials, or destructive commands without warnings How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator
Create a new skill following the agentskills.io specification (https://agentskills.io/specification).
Step 1: Gather requirements
Ask the user:
- What should the skill do?
- What tools or commands does it need?
- Does it need references, scripts, or assets?
If the user already provided enough context, skip asking and proceed.
Step 2: Choose a name
Rules for the name field:
- 1-64 characters
- Lowercase letters, numbers, hyphens only (
a-z,0-9,-) - Must NOT start or end with
- - Must NOT contain consecutive hyphens (
--) - Must match the parent directory name
Step 3: Write the description
Rules for the description field:
- 1-1024 characters
- Must describe WHAT the skill does AND WHEN to use it
- Include keywords that help semantic matching
Good:
description: Extract text and tables from PDF files, fill PDF forms, and merge multiple PDFs. Use when working with PDF documents or when the user mentions PDFs, forms, or document extraction.
Bad:
description: Helps with PDFs.
Step 4: Create the directory structure
.zeph/skills/<skill-name>/
├── SKILL.md # Required
├── scripts/ # Optional: executable scripts
├── references/ # Optional: detailed docs loaded on demand
└── assets/ # Optional: templates, schemas, data files
Step 5: Write SKILL.md
Use this template:
---
name: <skill-name>
description: <what it does and when to use it>
compatibility: <only if environment requirements exist>
metadata:
author: zeph
version: "1.0"
---
# <Skill Title>
<One-line summary of what this skill does.>
## Step 1: <First action>
<Instructions with code blocks showing exact commands or tool invocations.>
## Step 2: <Next action>
<Continue step-by-step. Keep instructions concrete and unambiguous.>
Optional frontmatter fields
| Field | When to use |
|---|---|
license |
Skill has specific licensing terms |
compatibility |
Skill requires specific binaries, network, or environment |
metadata |
Extra key-value pairs (author, version, tags) |
allowed-tools |
Pre-approve specific tools (experimental) |
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 · 127 lines · 75 tokens per session scan B 8724edac67c7
skill-creator is a skill published in the GitHub repository bug-ops/zeph (65 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 911 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
plugin-system
Generic plugin system for Python applications. Auto-discovery, validation, fault tolerance. Zero dependencies (Python stdlib only).
skill-creator
Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
simplicio-loop
Unified public entrypoint for Simplicio's body-of-work orchestration: core + loop in one command. Use when the user types /simplicio-loop, says "ralph loop", "keep iterating until done", "finish all open issues", or asks to drain a queue of work autonomously. Runtime-agnostic: binds a real stop-hook where the host…
simplicio-nest-gate
N-Nest protocol — multi-level gate-corrected agent tree. PRIME depth verification, BH port.port.port addressing, per-level confabulation catch.
simplicio-orient
Terminal-first execution — answer facts with the shell, never with the LLM. Use whenever a step needs a fact about the filesystem, git, processes, or system resources, or runs a build/test/lint/diff whose output would flood context. Substitutes deterministic shell/CLI calls for native LLM operations and clamps their…