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 agentmods add instructions/warpdotdev/oz-skills/agents-mdgit clone --depth 1 https://github.com/warpdotdev/oz-skillsWhat 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 | $0.00908 | $0.00908 |
| Opus 5 | $0.00454 | $0.00454 |
| Sonnet 5 | $0.00182 | $0.00182 |
| Haiku 4.5 | $0.00091 | $0.00091 |
Grade A, and why
oz-skills AGENTS.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 2d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to WARP (warp.dev) when working with code in this repository.
Repository Overview
This is the oz-skills repository - a public catalog of reusable Agent Skills for Warp AI agents and Oz. These are pre-built skills that external users can copy into their projects to teach agents about common workflows and best practices.
Agent Skills Standard
This repository follows the Agent Skills open standard. Agent Skills are folders containing a SKILL.md file with YAML frontmatter and markdown instructions that agents can discover and use.
For comprehensive details about the skills format and usage patterns, see wip/warp-skills-overview.md.
Repository Structure
All skills are stored in the .agents/skills/ directory. Each skill has its own subdirectory:
.agents/skills/
├── docs-update/
│ └── SKILL.md
├── another-skill/
│ └── SKILL.md
└── ...
Skill File Format
Each skill must have a SKILL.md file with this structure:
---
name: skill-name
description: Imperative summary sentence. Use when sentence.
---
# Skill Title
Your instructions, examples, and guidance here in markdown format.
Required Fields
- name: Kebab-case identifier (e.g.,
docs-update,rust-testing,api-conventions) - description: Two sentences in a strict pattern:
- Sentence 1: Imperative verb + what the skill does (e.g.,
Audit...,Build...,Test...) - Sentence 2: Starts with
Use when...and describes trigger scenarios
- Sentence 1: Imperative verb + what the skill does (e.g.,
Skill Metadata Style Guide (Canonical)
Use these rules whenever creating or editing a skill:
namemust be kebab-case and exactly match the skill directory namedescriptionmust be exactly two sentencesdescriptionsentence 1 must start with an imperative verb (Build,Audit,Test,Optimize,Triage,Generate,Investigate, etc.)descriptionsentence 2 must start withUse when...- Keep
descriptionconcise and concrete; avoid filler and unnecessary quotes SKILL.mdmust include a single H1 in Title Case- H1 should reflect the skill's human-readable purpose (for example,
# Web Performance Audit)
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.
- 2d ago First seen · 122 lines · 908 tokens per session scan A db21fd4315ee
oz-skills AGENTS.md is an instructions file published in the GitHub repository warpdotdev/oz-skills (823 stars, last pushed 17d ago), licensed MIT. It adds 908 tokens to every session, about $0.0045 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.