Borrowing it
Nothing to install: this file belongs to tmusser/ai-engineering-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/tmusser/ai-engineering-skills/main/AGENTS.mdgit clone --depth 1 https://github.com/tmusser/ai-engineering-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/tmusser/ai-engineering-skills/agents-md)<a href="https://agentmods.dev/instructions/tmusser/ai-engineering-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/tmusser/ai-engineering-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.00385 | $0.00385 |
| Opus 5 | $0.00192 | $0.00192 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
ai-engineering-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.
What it actually says
Agent Instructions
This repo is mostly Markdown process artifacts plus small standard-library Python scripts.
Preserve concise, actionable wording.
Do not add unnecessary framework complexity.
Do not copy from external skill repos.
Keep each skill self-contained.
When editing a skill, update related templates if needed.
Route-first context loading
Resolve the task route before loading workflow guidance.
- Load only the selected skills and directly relevant current-state or project files by default.
- Do not preload the full skill pack merely because it is installed.
- Expand context when the task spans routes, a compatibility seam requires it, or verification exposes missing context.
- Searches and reads remain allowed unless explicitly forbidden. This rule limits the default working set, not discovery.
- Treat current project state as more authoritative than templates and examples.
See docs/context-isolation.md for the full loading and expansion rules.
Run validation after changes:
python -m py_compile scripts/validate_repo.py
python -m py_compile scripts/install_claude_code.py
python scripts/validate_repo.py
Prefer small diffs.
Preserve the MIT license and acknowledgments.
Do not add generated marketing fluff.
When editing handoff behavior, preserve Workflow state: active modes, current phase, current loop, next gate, context risk, and active hypothesis. Do not expand handoff into a transcript summary.
Quality standards
Every skill must include YAML frontmatter:
namedescription
Every skill must include:
- Purpose
- When to use
- Inputs
- Workflow
- Outputs
- Stop conditions
- Anti-patterns
Every template must be short and directly usable.
Every example must show a concrete use case.
Every install path must remain portable across tools.
Claude Code support is first-class.
Codex support is maintained.
Manual install must remain possible because skills are plain folders with SKILL.md files.
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 · 71 lines · 385 tokens per session scan A 7352f1b049c7
ai-engineering-skills AGENTS.md is an instructions file published in the GitHub repository tmusser/ai-engineering-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 385 tokens to every session, about $0.0019 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.