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 ouro-ai-labs/ouro --skill skill-creatorgit clone --depth 1 https://github.com/ouro-ai-labs/ouroWrote 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/ouro-ai-labs/ouro/skill-creator)<a href="https://agentmods.dev/skills/ouro-ai-labs/ouro/skill-creator"><img src="https://agentmods.dev/badge/skills/ouro-ai-labs/ouro/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/ouro-ai-labs/ouro/skill-creator"><img src="https://agentmods.dev/badge/skills/ouro-ai-labs/ouro/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 124 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 199 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 124 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.
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.00042 | $0.01442 |
| Opus 5 | $0.00021 | $0.00721 |
| Sonnet 5 | $0.00008 | $0.00288 |
| Haiku 4.5 | $0.00004 | $0.00144 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator
This skill guides you through creating effective ouro skills that extend the agent's capabilities.
Core Principles
Concise is Key
Every line in a skill costs tokens. Write tightly:
- Remove filler words ("please", "you should", "it's important to")
- Use imperative/infinitive form ("Run script" not "You should run the script")
- Prefer bullet lists over prose
- Skip obvious context the LLM already knows
Set Appropriate Degrees of Freedom
- Too specific = rigid, breaks on edge cases
- Too broad = vague, inconsistent outputs
- Just right = clear guardrails with room for judgment
Example: Instead of "Always use pytest", say "Use pytest for Python tests; adapt for other languages."
Anatomy of a Skill
Every skill consists of a required SKILL.md file and optional bundled resources:
skill-name/
├── SKILL.md (required)
│ ├── YAML frontmatter metadata (required)
│ │ ├── name: (required)
│ │ └── description: (required)
│ └── Markdown instructions (required)
└── Bundled Resources (optional)
├── scripts/ - Executable code (Python/Bash/etc.)
├── references/ - Documentation to load into context as needed
└── assets/ - Files used in output (templates, icons, fonts, etc.)
SKILL.md (required)
Every SKILL.md consists of:
- Frontmatter (YAML): Contains
nameanddescriptionfields. These are the only fields that ouro reads to determine when the skill gets used, thus it is very important to be clear and comprehensive in describing what the skill is, and when it should be used. - Body (Markdown): Instructions and guidance for using the skill. Only loaded AFTER the skill triggers.
Bundled Resources (optional)
Skills can include three types of resources:
| Type | Purpose | When to use |
|---|---|---|
scripts/ |
Executable code (Python, Bash, etc.) | Reusable automation, data processing, API calls |
references/ |
Documentation files (.md) | Schemas, API docs, style guides |
assets/ |
Output files (templates, images) | Boilerplate projects, icon sets, fonts |
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.
- 10d ago First seen · 213 lines · 42 tokens per session scan A f1a74965bcdf
skill-creator is a skill published in the GitHub repository ouro-ai-labs/ouro (44 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 1,442 once invoked, about $0.0002 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
ai-style
A Chinese-language writing guide for producing or revising reader-facing text such as product announcements, public-account articles, emails, and README files. It focuses on reducing patterns that make writing sound machine-generated.
triage
A task-routing guide that identifies goals, dependencies, and acceptance conditions before work begins. It orders work as research, calculation or execution, and writing.
writing
A writing guide for turning verified facts and calculations into finished text for a specific audience. It follows the requested language, structure, and length.
data_analysis
A data-analysis guide for doing mathematical calculations and descriptive statistics with confirmed, sourced data. Descriptive statistics summarise data using measures such as totals, averages, or ranges.
coding
A coding guide for writing and running Python programs in a sandbox. It requires scripts to be small and reproducible, with their actual output or errors reported.
agent-mode
Unified tool for managing agent LLM modes (add, remove, update, list, switch).