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/event4u-app/agent-config/copilot-instructionsgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/copilot-instructions)<a href="https://agentmods.dev/instructions/event4u-app/agent-config/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/event4u-app/agent-config/copilot-instructions.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.01848 | $0.01848 |
| Opus 5 | $0.00924 | $0.00924 |
| Sonnet 5 | $0.00370 | $0.00370 |
| Haiku 4.5 | $0.00185 | $0.00185 |
Grade A, and why
agent-config copilot-instructions.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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Repository Instructions — event4u/agent-config
This repository is the event4u/agent-config package: shared agent configuration (skills, rules, commands, guidelines, templates) for AI coding tools. It is a distribution package, not an application of any framework (Laravel, Symfony, Next.js, etc.).
For Copilot Chat users: Rich context lives in
.augment/(rules, skills, guidelines) andAGENTS.mdat the repo root. Ask Copilot Chat to read those files. The instructions below are self-contained for Copilot Code Review, which cannot follow links.
✅ What this repo contains
- Bash scripts under
src/scripts/install.shandsrc/scripts/condense.sh. - Python 3.10+ tooling under
scripts/— condensation driver, linters (skills, references, portability, readme), installer bridge. - Markdown content under
.agent-src.uncondensed/(authoring layer) and.augment/(generated output). Edit the former, never the latter. - pytest test suite under
tests/.
No application source code — no framework app code (Laravel, Symfony, Next.js, Express, etc.), no JavaScript runtime deps. If you see framework-specific suggestions in a PR touching this repo, they are wrong.
✅ Scope Control
- Do not introduce architectural changes unless explicitly requested.
- Do not replace existing patterns with alternatives.
- Do not suggest new libraries unless explicitly requested.
- Stay within the established structure.
✅ Portability rules for this package
- Never reference a specific consumer project (project names, domains,
internal tools, customers) in
.augment/,.agent-src.uncondensed/, rootAGENTS.md, or.github/copilot-instructions.md. Everything here must work in any consumer project. - Project-specific behavior belongs in a consumer's own
.agent-settings.yml,AGENTS.md, oragents/directory — not in this package. - The portability checker (
src/scripts/check_portability.py) enforces this in CI.
✅ Editing .augment/ — source-of-truth rule
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 · 163 lines · 1,848 tokens per session scan A 38e2855a12e5
agent-config copilot-instructions.md is an instructions file published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 1,848 tokens to every session, about $0.0092 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
Meta_Kim AGENTS.md
AGENTS.md instructions for KimYx0207/Meta_Kim, covering metakim for codex, fast read, codex output rules, what this repository is and source of truth.
Meta_Kim CLAUDE.md
Claude Code instructions for KimYx0207/Meta_Kim, covering metakim for claude code, fast read, what this repository is, claude code's role and canonical vs runtime files.
FCoP AGENTS.md
AGENTS.md instructions for joinwell52-AI/FCoP, covering fcop protocol rules · agent-host-neutral copy, fcop rules · fcop 协议规则, 目的 / purpose, fcop 的定位与七大核心概念 / protocol position & seven core concepts and 协议层定位 / protocol layer.
FCoP CLAUDE.md
Claude Code instructions for joinwell52-AI/FCoP, covering fcop protocol rules · agent-host-neutral copy, fcop rules · fcop 协议规则, 目的 / purpose, fcop 的定位与七大核心概念 / protocol position & seven core concepts and 协议层定位 / protocol layer.
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.