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 Azzurroooo/rind --skill skill-creatorgit clone --depth 1 https://github.com/Azzurroooo/rindWrote 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/azzurroooo/rind/skill-creator)<a href="https://agentmods.dev/skills/azzurroooo/rind/skill-creator"><img src="https://agentmods.dev/badge/skills/azzurroooo/rind/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/azzurroooo/rind/skill-creator"><img src="https://agentmods.dev/badge/skills/azzurroooo/rind/skill-creator.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.00042 | $0.00620 |
| Opus 5.5 | $0.00017 | $0.00248 |
| Sonnet 5.5 | $0.00008 | $0.00124 |
| Haiku 4.5 | $0.00004 | $0.00062 |
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 3d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating a Skill
A Skill is a folder with a SKILL.md. Its frontmatter is always visible in the skill catalog; the body is read only when a task needs it, and files beside it only when the body points to them. Keep each layer as small as it can be.
Where it goes
- This folder only:
.rind/skills/<name>/SKILL.mdunder the current working directory. - Every folder for this user:
~/.rind/skills/<name>/SKILL.md.
Ask which one when the user has not said. To change an existing Skill, edit the SKILL.md at its catalog location, except under ~/.rind/skills/.system: Rind installs those built-in Skills and replaces them on update. To change a built-in Skill, create one with the same name in ~/.rind/skills/ instead; it overrides the built-in one.
Layout
<name>/
├── SKILL.md required: frontmatter and instructions
├── scripts/ optional: code the instructions tell the agent to run
├── references/ optional: long material read only when needed
└── assets/ optional: templates and files copied into output
Reference these files by paths relative to the Skill folder, for example references/api.md.
SKILL.md
---
name: <name>
description: <what it does>. Use when <the situations that should trigger it>.
---
# <Title>
<Steps, rules and examples the agent follows.>
name: lowercase letters, digits and hyphens, at most 64 characters, the same as the folder name.description: one or two sentences, at most 1024 characters. It is the only text the model sees before choosing the Skill, so say both what it does and when to use it.- Optional
disable-model-invocation: truekeeps it out of the catalog; it then runs only when the user types/skill:<name>.
Writing the body
- Write instructions for another capable agent: what to do, in what order, and what to check. Skip general knowledge it already has.
- Prefer one concrete example to a paragraph of explanation.
- Move long reference material, schemas and variants into
references/and say when to read each file. - Put repeated or fragile steps into
scripts/and say how to run them.
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.
- 3d ago First seen · 58 lines · 42 tokens per session scan A c92f20be2a97
skill-creator is a skill published in the GitHub repository Azzurroooo/rind (18 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 620 once invoked, about $0.0002 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-10-13.
Other skills, from other repositories
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
fleet-manager
Use when managing, triaging, restarting, escalating, or summarizing Codewhale fleet runs and workers.
handoff
Write a compact, decision-ready handoff so the next session (or the user) can continue without reconstructing the current one. Use when the session is ending, context is running low, the user asks for a handoff / 'pass the baton' / 'hand off', or a long-running operation needs a durable state checkpoint.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-close-issues
Close resolved Codewhale issues only after verifying the landed commit/behavior, with a positive crediting comment; never from title alone.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.