Borrowing it
Nothing to install: this file belongs to organvm-iv-taxis/a-i--skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/organvm-iv-taxis/a-i--skills/main/.github/instructions/02-skill-format.instructions.mdgit clone --depth 1 https://github.com/organvm-iv-taxis/a-i--skillsWrote 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/instructions/organvm-iv-taxis/a-i--skills/02-skill-format)<a href="https://agentmods.dev/instructions/organvm-iv-taxis/a-i--skills/02-skill-format"><img src="https://agentmods.dev/badge/instructions/organvm-iv-taxis/a-i--skills/02-skill-format/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/instructions/organvm-iv-taxis/a-i--skills/02-skill-format"><img src="https://agentmods.dev/badge/instructions/organvm-iv-taxis/a-i--skills/02-skill-format.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.00575 | $0.00575 |
| Opus 5 | $0.00287 | $0.00287 |
| Sonnet 5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
a-i--skills 02-skill-format.instructions.md 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 11d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Format Instructions
SKILL.md File Structure
Every skill must have a SKILL.md file as its entry point.
Required YAML Frontmatter
---
name: my-skill-name
description: Clear, task-focused description of what the skill does
---
Optional YAML Fields
---
name: my-skill-name
description: What the skill does and when to use it
license: Apache-2.0
allowed-tools:
- bash
- edit
- view
metadata:
author: Your Name
version: 1.0.0
category: development
---
Naming Rules
- Skill name: Lowercase, hyphen-separated (kebab-case)
- Must match directory name exactly
- Pattern:
[a-z0-9]+(-[a-z0-9]+)* - Examples:
algorithmic-art,mcp-builder,web-artifacts-builder
Description Guidelines
- Write as a complete sentence
- Focus on the task or capability
- Be concise but informative
- Good: "Create generative art using p5.js with seeded randomness and particle systems"
- Bad: "Art skill" or "This skill helps you make art and stuff"
Markdown Body
After the frontmatter, write clear instructions:
- Purpose: What the skill does
- Usage: How an agent should use it
- Examples: Concrete use cases
- Resources: Links to scripts, templates, or references
Keep examples concise and actionable. Prefer ASCII content unless the domain requires otherwise.
Template Example
---
name: template-skill
description: A basic template for creating new skills
---
# Template Skill
This skill provides a starting point for creating new skills.
## Usage
Use this skill when you need to create a new skill from scratch.
## Instructions
1. Copy this template directory
2. Rename to your skill name (kebab-case)
3. Update the frontmatter
4. Add your instructions
5. (Optional) Add scripts and resources
## Examples
**Creating a simple skill:**
- Copy template-skill to my-new-skill
- Edit SKILL.md with your content
- Run refresh script
**Adding scripts:**
- Create scripts/ subdirectory
- Add Python/bash scripts
- Document usage in SKILL.md
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.
- 11d ago First seen · 107 lines · 575 tokens per session scan A 241d5f7d212e
a-i--skills 02-skill-format.instructions.md is an instructions file published in the GitHub repository organvm-iv-taxis/a-i--skills (17 stars, last pushed 15d ago), licensed Apache-2.0. It adds 575 tokens to every session, about $0.0029 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).