Borrowing it
Nothing to install: this file belongs to tartinerlabs/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/tartinerlabs/skills/main/AGENTS.mdgit clone --depth 1 https://github.com/tartinerlabs/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/tartinerlabs/skills/agents-md)<a href="https://agentmods.dev/instructions/tartinerlabs/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/tartinerlabs/skills/agents-md.svg" alt="Measured on agentmods" 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.02135 | $0.02135 |
| Opus 5 | $0.01068 | $0.01068 |
| Sonnet 5 | $0.00427 | $0.00427 |
| Haiku 4.5 | $0.00214 | $0.00214 |
Grade A, and why
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 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Canonical guidance for coding agents working in this repository. Claude Code additions live in CLAUDE.md; everything here applies to every agent.
Project Overview
Repository: https://github.com/tartinerlabs/skills
Package: @tartinerlabs/skills
A collection of agent skills distributed via Claude Code, Codex, Cursor, Antigravity, and skills.sh. Each skill is a markdown file with YAML frontmatter following the Agent Skills spec.
Development
- Tooling: stdlib-only Go plus plain shell git hooks — the repo deliberately avoids npm dependencies to keep the supply-chain surface minimal
- Git hooks: plain shell hooks in
.githooks/(enable withgit config core.hooksPath .githooks) —commit-msgenforces conventional commits (no scope, max 50-char header),pre-commitruns GitLeaks secrets detection - Checks:
go run ./scripts/validate-skillsandgo test ./... - Releases: Automated via release-please on push to
main— maintains a release PR from conventional commits; merging it bumps versions, updatesCHANGELOG.md, and creates the GitHub release
Skill Format
Each skill lives in skills/<name>/SKILL.md:
---
name: skill-name
description: What it does and when to use it
license: MIT
allowed-tools: Space-delimited list of permitted tools
model: sonnet
effort: medium
compatibility: What the skill really requires
metadata:
short-description: Short display name for Codex
---
[Instructions the agent follows when the skill is active]
Frontmatter Fields
Fields split into two groups. Portable fields (name, description, license, compatibility, metadata, allowed-tools) come from the Agent Skills spec and are the only ones non-Claude channels can act on. Claude-Code-only fields (model, effort, context, agent) are ignored gracefully everywhere else. go run ./scripts/validate-skills enforces the portable group — every skill must carry name, description, license, compatibility, and metadata.short-description.
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 · 96 lines · 2,135 tokens per session scan A 32521ef1c1ac
skills AGENTS.md is an instructions file published in the GitHub repository tartinerlabs/skills (7 stars, last pushed 15d ago), licensed MIT. It adds 2,135 tokens to every session, about $0.0107 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-31.
Other instructions, from other repositories
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).
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.
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).
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.