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 donggua-zen/guada --skill skill-creatorgit clone --depth 1 https://github.com/donggua-zen/guadaWrote 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/donggua-zen/guada/skill-creator)<a href="https://agentmods.dev/skills/donggua-zen/guada/skill-creator"><img src="https://agentmods.dev/badge/skills/donggua-zen/guada/skill-creator.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 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 262 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 455 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.
- medium Rogue Agent · line 252 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Agent Snooping · line 320 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00029 | $0.04658 |
| Opus 5 | $0.00015 | $0.02329 |
| Sonnet 5 | $0.00006 | $0.00932 |
| Haiku 4.5 | $0.00003 | $0.00466 |
Grade A, and why
skill-creator 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 8d 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 — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator — Comprehensive Skill Authoring Guide
Overview
This skill guides you through the complete process of creating a new AI skill for the system. A skill is a reusable instruction bundle that teaches the AI how to perform a specific type of task. Skills follow the AgentSkills open specification.
Skills use progressive disclosure to manage context efficiently:
- L1 — Metadata (~100 tokens):
name+descriptionloaded at startup for all skills - L2 — Instructions (SKILL.md body): Loaded only when the skill is activated
- L3 — Resources (scripts/, references/, assets/): Loaded on demand
1. Skill Directory Structure
1.1 Full File Layout
<skill-name>/ # Directory name = skill name (lowercase + hyphens)
├── SKILL.md # Required: metadata + instructions
├── scripts/ # Optional: executable code
│ ├── script.py
│ ├── script.sh
│ └── ...
├── references/ # Optional: reference docs loaded on demand
│ ├── api-spec.md
│ ├── configuration-guide.md
│ └── ...
├── assets/ # Optional: templates, configs, resources
│ ├── template.json
│ ├── icon.svg
│ └── ...
└── ... # Any additional files or directories
1.2 Minimal Structure (always valid)
<skill-name>/
└── SKILL.md
A single SKILL.md file is all that's required. The optional directories are for organizing larger skills.
1.3 Location by Source Type
| Source | Directory | Persistence |
|---|---|---|
| System (built-in) | {SKILLS_DIR}/.system/<name>/ |
Synced from bundled-skills/ on startup, overwritten on upgrade, cannot be uninstalled |
| User (installed) | {SKILLS_DIR}/<name>/ |
Installed by user, can be updated/uninstalled |
SKILLS_DIR defaults to ~/.guada/skills/ (where ~ is the user's home directory, e.g. C:\Users\<username>\.guada\skills on Windows); configurable via SKILLS_DIR environment variable.
What ships with it
1 file 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.
- 8d ago First seen · 569 lines · 29 tokens per session scan A dffb44dd9623
skill-creator is a skill published in the GitHub repository donggua-zen/guada (57 stars, last pushed 24d ago), licensed MIT. It adds 29 tokens to every session and 4,658 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-30.
Other skills, from other repositories
skill-authoring
Author SKILL.md skills: frontmatter, validator limits, structure.
author-skill
Use when authoring a NEW rsc skill or editing an existing one — scoping it to one job, writing the description that decides whether it ever loads, splitting the body into references/, writing its evals, auditing it against the rubric. NOT building a product feature (that is specify) and NOT designing an agent loop…
skill-authoring
Creates and structures SKILL.md files for AI coding agents, including YAML frontmatter, trigger phrases, directive instructions, decision trees, code examples, and verification checklists. Use when the user asks to write a new skill, create a skill file, author agent capabilities, generate skill documentation, or…
writing-skills
Authors new SKILL.md files that conform to the dojo spec.
skill-creator
A guide for creating and editing reusable instruction packages called skills. A skill gives an agent the knowledge and workflow needed for a particular kind of task.
authoring-skills-and-rules
Author Skills (SKILL.md) and rules/instructions across Claude Code, Cursor, OpenCode, Codex, and GitHub Copilot. Covers frontmatter, file layout, activation model, cross-platform mirroring, and the universal craft: progressive disclosure, trigger-rich descriptions (context pointers), leading words, token budget…