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/carofi-auto/agent-skills/agents-mdgit clone --depth 1 https://github.com/carofi-auto/agent-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/carofi-auto/agent-skills/agents-md)<a href="https://agentmods.dev/instructions/carofi-auto/agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/carofi-auto/agent-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.00948 | $0.00948 |
| Opus 5 | $0.00474 | $0.00474 |
| Sonnet 5 | $0.00190 | $0.00190 |
| Haiku 4.5 | $0.00095 | $0.00095 |
Grade A, and why
agent-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 5d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to AI coding agents (Claude Code, Cursor, Copilot, Cline, etc.) when working with code in this repository.
Repository Overview
A collection of agent skills published by carofi-auto. Each skill packages domain knowledge into a format that AI coding agents can install and use automatically.
Skills are plain markdown — no build step, no dependencies.
Directory Structure
carofi-auto/agent-skills/
├── README.md # skill directory and install commands
├── AGENTS.md # this file
├── CLAUDE.md # Claude Code-specific guidance (same content)
├── LICENSE # MIT
└── {skill-name}/ # one directory per skill, kebab-case
├── SKILL.md # required: skill definition and instructions
└── references/ # optional: supporting docs read on demand
└── {topic}.md
Adding a New Skill
1. Create the skill directory
Use kebab-case. The directory name becomes the --skill argument at install time.
{skill-name}/
├── SKILL.md
└── references/ # add only if SKILL.md would exceed ~400 lines without it
└── {topic}.md
2. Write SKILL.md
Required frontmatter:
---
name: {skill-name}
description: "{One sentence written as a trigger condition — when should an agent activate this skill? Include key nouns: library names, env var names, domain terms.}"
---
Body structure (adapt sections to the skill's complexity):
# {Skill Title}
> **Attribution:** {Credit the upstream source if this skill is built on
> official documentation. Link to the source.}
Brief one-paragraph description of what this skill covers.
## When this skill activates
- Bullet list of concrete trigger signals (env vars, keywords, file patterns)
## Non-negotiable rules
Numbered list of rules the agent must enforce regardless of user intent.
Security rules, data integrity rules, and irreversibility warnings belong here.
## Before writing any integration code
Table mapping tasks to reference files (if references/ exists).
## {Any domain-specific sections}
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.
- 5d ago First seen · 121 lines · 948 tokens per session scan A 9fdd3d8f75bd
agent-skills AGENTS.md is an instructions file published in the GitHub repository carofi-auto/agent-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 948 tokens to every session, about $0.0047 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
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.
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.
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).