Borrowing it
Nothing to install: this file belongs to onehorizonai/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/onehorizonai/skills/main/AGENTS.mdgit clone --depth 1 https://github.com/onehorizonai/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/onehorizonai/skills/agents-md)<a href="https://agentmods.dev/instructions/onehorizonai/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/onehorizonai/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.00791 | $0.00791 |
| Opus 5 | $0.00396 | $0.00396 |
| Sonnet 5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
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 6d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guide
This repo contains one plugin. skills/ is the source of truth for skill instructions. App-specific manifests live at the repo root and are generated from plugin.json. Do not edit generated files directly.
Structure
skills/
{skill-name}/
SKILL.md
agents/openai.yaml
assets/
assets/ # Shared plugin assets
hooks/ # Shared hook scripts
scripts/
build-manifests.mjs # Regenerates app-specific manifests
validate.mjs # Validates manifests and skill metadata
validate-links.mjs # Validates local refs and external URLs
plugin.json # Canonical plugin manifest
.mcp.json # Shared MCP server config
copilot-hooks.json # Shared hook manifest
.cursor-plugin/plugin.json # Generated Cursor manifest
.codex-plugin/plugin.json # Generated Codex manifest
.claude-plugin/marketplace.json # Claude marketplace
.agents/plugins/marketplace.json # Local Codex marketplace
.github/plugin/marketplace.json # GitHub/Copilot marketplace
Working with skills
Each skill lives at skills/{skill-name}/SKILL.md with frontmatter and agent instructions.
SKILL.md format
---
name: {skill-name} # Matches the folder name; no plugin prefix
description: {One sentence with trigger phrases like "prep my standup" or "list blockers".}
---
# Skill title
What this skill does, when to use it, and which nearby skill owns adjacent work.
## Instructions
Step-by-step instructions for the agent to follow when this skill is invoked.
Rules
namemust match the folder name exactly; do not add a plugin namespace prefix- The slash command is built automatically:
/{plugin-name}:{skill-name} - Keep
SKILL.mdshort because the full file loads into context on every invocation descriptioncontrols when the agent picks up the skill; write it with concrete trigger phrases- Edit skills in
skills/only - Don't edit generated app manifests unless you're also updating
scripts/build-manifests.mjs
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.
- 6d ago First seen · 105 lines · 791 tokens per session scan A 36d966010c61
skills AGENTS.md is an instructions file published in the GitHub repository onehorizonai/skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 791 tokens to every session, about $0.0040 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
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).
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).
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.
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.