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/remix-run/agent-skills/agents-mdgit clone --depth 1 https://github.com/remix-run/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/remix-run/agent-skills/agents-md)<a href="https://agentmods.dev/instructions/remix-run/agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/remix-run/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 | $0.00882 | $0.00882 |
| Opus 5 | $0.00441 | $0.00441 |
| Sonnet 5 | $0.00176 | $0.00176 |
| Haiku 4.5 | $0.00088 | $0.00088 |
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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring Agent Skills
Guidelines for creating skills in this repository.
Directory Structure
Skills live in the skills/ directory:
skills/
└── skill-name/
├── SKILL.md # Required - main entry point
└── references/ # Optional - detailed topic docs
Naming
Use lowercase with hyphens. The directory name must match the name field in SKILL.md frontmatter:
react-router-framework-modereact-router-data-moderemix
SKILL.md Format
Follow the Agent Skills specification.
Required Frontmatter
---
name: skill-name
description: What this skill does. Be specific about when agents should activate it.
license: MIT
---
Recommended Sections
- Title & Intro - Brief overview of the skill
- When to Apply - Bullet list of specific trigger conditions
- References - Table mapping topics to reference files
- Version Compatibility - Feature/version requirements (if applicable)
- Critical Patterns - Most important patterns with code examples
- Further Documentation - Links to official docs
Example structure:
# Skill Name
Brief description of what the skill covers.
## When to Apply
- Specific condition that triggers this skill
- Another trigger condition
- Yet another trigger
## References
| Reference | Use When |
| --------------------- | -------------- |
| `references/topic.md` | Working with X |
| `references/other.md` | Implementing Y |
## Critical Patterns
Show the most important patterns here with code examples.
Size Guidelines
- Keep SKILL.md under 500 lines
- Move detailed reference material to
references/ - Include only the most critical patterns inline
Reference Files
Reference files provide detailed guidance on specific topics.
Frontmatter
---
title: Topic Name
description: Brief description of what this reference covers
tags: [relevant, searchable, tags]
---
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 · 165 lines · 882 tokens per session scan A 4ade44a3232b
agent-skills AGENTS.md is an instructions file published in the GitHub repository remix-run/agent-skills (137 stars, last pushed 2mo ago), licensed MIT. It adds 882 tokens to every session, about $0.0044 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
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.
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).