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/sleeyax/promptfiles/agents-mdgit clone --depth 1 https://github.com/sleeyax/promptfilesWrote 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/sleeyax/promptfiles/agents-md)<a href="https://agentmods.dev/instructions/sleeyax/promptfiles/agents-md"><img src="https://agentmods.dev/badge/instructions/sleeyax/promptfiles/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.01506 | $0.01506 |
| Opus 5 | $0.00753 | $0.00753 |
| Sonnet 5 | $0.00301 | $0.00301 |
| Haiku 4.5 | $0.00151 | $0.00151 |
Grade A, and why
promptfiles 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 4d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to AI agents when working with code in this repository.
Project Overview
This is a curated collection of AI skills and agent definitions. There are no build steps, tests, or dependencies — the repository contains only static markdown files with YAML frontmatter.
Agents are Claude Code subagents, installed by symlinking into ~/.claude/agents/; scripts/install-codex-agents.sh generates Codex TOML equivalents from the same markdown files. Skills (used as Claude Code's replacement for slash commands in this repo) are installed via the skills npm CLI.
The repo also doubles as a Claude Code marketplace hosting one plugin, sleeyax-skills@sleeyax, that bundles every skill, both agents, and the output styles. See Plugin manifests.
Managing the local install
Prefer the skills CLI for anything that changes what is installed on the user's machine.
Global installs live in ~/.agents/skills/<name>/, and each agent directory symlinks to them.
npx skills list -g # what is installed globally
npx skills add . -s '*' # install every skill from this working copy
npx skills add . -l # list what's installable here, without installing
npx skills update -g # pull the latest versions
npx skills remove --global <name>... -y # uninstall by skill name
Install from ., not from sleeyax/promptfiles — the latter pulls the published GitHub copy and silently ignores uncommitted local work.
remove and add are interactive by default, but the CLI detects it is running under an agent and falls back to a non-interactive run.
Pass -y anyway so the command can't block.
-y on add also skips the scope prompt and auto-detects, so pass -g alongside it when the target is the global install.
If the CLI can't do the job — it's unavailable, the command fails, or the install is in a state it won't reconcile — edit ~/.agents/skills/ and the symlinks under ~/.claude/skills/ directly, and say that you did.
Leave no dangling symlinks behind.
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.
- 4d ago First seen · 80 lines · 1,506 tokens per session scan A c3f7735f7fc7
promptfiles AGENTS.md is an instructions file published in the GitHub repository sleeyax/promptfiles (2 stars, last pushed 5d ago), licensed MIT. It adds 1,506 tokens to every session, about $0.0075 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.
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.