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/tecnomanu/agent-rules-kit/copilot-instructionsgit clone --depth 1 https://github.com/tecnomanu/agent-rules-kitWhat 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.03784 | $0.03784 |
| Opus 5 | $0.01892 | $0.01892 |
| Sonnet 5 | $0.00757 | $0.00757 |
| Haiku 4.5 | $0.00378 | $0.00378 |
Grade C, and why
agent-rules-kit copilot-instructions.md scanned grade C with 1 finding 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 2d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- In the future: or using the translations system --> How it starts
The opening of the file, as written. The whole thing — 476 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Overview & Guidelines
This repository contains agent‑rules‑kit, a CLI tool and template set that bootstraps Cursor rules for multiple stacks. The rules in this folder govern the maintenance of this very project.
| Topic | Quick rule |
|---|---|
| CLI changes | Update code in cli/services/ modules and cli/index.js; add unit and integration tests. |
| Templates | Follow folder layout: templates/global/, templates/stacks/<stack>/base/, templates/stacks/<stack>/architectures/, templates/stacks/<stack>/v*/. |
| Config | Keep templates/kit-config.json as single source of truth for globs, version ranges & default architectures. |
| Releases | Bump package.json + CHANGELOG. Tag using vx.y.z. |
| Language | All code, documentation, and files must be written in English, even if communicating with the agent in another language. |
Language Policy
While you may interact with the agent in any language, all project files, code, comments, documentation, and rules must be written in English. This ensures consistency and maintainability across the project. When working with the Agent Rules Kit:
- Write all code, comments, and docstrings in English
- Create documentation files in English
- Use English for variable names, function names, and other identifiers
- Use English for commit messages and pull requests
- Keep configuration files in English
For example, if you're communicating with the agent in Spanish, the agent should respond in Spanish, but any generated or modified code must still be in English.
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.
- 2d ago First seen · 476 lines · 3,784 tokens per session scan C 439548338c81
agent-rules-kit copilot-instructions.md is an instructions file published in the GitHub repository tecnomanu/agent-rules-kit (35 stars, last pushed 11mo ago), licensed ISC. It adds 3,784 tokens to every session, about $0.0189 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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.
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).
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.