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/thearchitectit/agent-guardrails-template/copilot-instructionsgit clone --depth 1 https://github.com/TheArchitectit/agent-guardrails-templateWrote 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/thearchitectit/agent-guardrails-template/copilot-instructions)<a href="https://agentmods.dev/instructions/thearchitectit/agent-guardrails-template/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/thearchitectit/agent-guardrails-template/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.1 | $0.00852 | $0.00852 |
| Opus 5 | $0.00426 | $0.00426 |
| Sonnet 5 | $0.00170 | $0.00170 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
agent-guardrails-template 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 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions
These instructions apply to all Copilot completions, suggestions, and chat interactions in this repository.
The Four Laws of Agent Safety
- Read Before Editing - Never suggest modifications without reading the file first
- Stay in Scope - Only work on files within the authorized task scope
- Verify Before Committing - Ensure suggested code compiles, passes lint, and is tested
- Halt When Uncertain - Ask for clarification instead of guessing
Code Generation Rules
Scope (MANDATORY)
- Only modify files explicitly requested by the user
- Do not refactor unrelated code "while I'm here"
- Do not add new files unless asked
- Do not delete files unless asked
- When scope is unclear: ask for confirmation
Production-First
- Production code must be written before test code
- Tests written against existing production code, not stubs
- Infrastructure code comes after both production and tests
Error Handling
- Validate inputs and handle errors explicitly
- Return meaningful error messages
- Never silently swallow exceptions
- Prefer explicit error returns over panics/exceptions
Security
- Never suggest committing secrets, keys, or credentials
- Never suggest .env files in version control
- Validate all external inputs
- Use parameterized queries, never string concatenation for SQL
Forbidden Patterns
NEVER suggest code that:
- Modifies files that haven't been read
- Mixes test and production environments
- Commits secrets or credentials
- Runs untested code in production
- Makes assumptions about user intent
Three Strikes Rule
When a suggestion is rejected or produces errors:
- 1st failure: Adjust approach and retry
- 2nd failure: Try completely different approach
- 3rd failure: HALT and ask user for guidance
File Headers
Include at the top of new files:
// File: <filename>
// Purpose: <one-line description>
// Created: <date>
// Author: AI-assisted (see git history)
Or equivalent in the target language.
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 · 132 lines · 852 tokens per session scan A f7aa497457ba
agent-guardrails-template copilot-instructions.md is an instructions file published in the GitHub repository TheArchitectit/agent-guardrails-template (79 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 852 tokens to every session, about $0.0043 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-30.
Other instructions, from other repositories
AionUi AGENTS.md
AGENTS.md instructions for iOfficeAI/AionUi, covering aionui - project guide, code conventions, file & directory structure, naming and ui library & icons.
bifrost AGENTS.md
AGENTS.md instructions for maximhq/bifrost, covering agents.md — bifrost ai gateway, what is bifrost?, repository layout, go workspace and build, test & dev commands.
langwatch CLAUDE.md
Claude Code instructions for langwatch/langwatch, covering langwatch, before you implement anything, development environment, running with no container runtime and local dev by hostname — thuishaven / portless (recommended).
parlant CLAUDE.md
Instructions for emcie-co/parlant: This is the main repo of Parlant (https://parlant.io).
lobehub AGENTS.md
AGENTS.md instructions for lobehub/lobehub, covering lobehub development guidelines, tech stack, agent skills, project structure and spa routes and features.
skyvern CLAUDE.md
Claude Code instructions for Skyvern-AI/skyvern, covering claude.md, development commands, python backend commands, code quality & testing and frontend commands (in skyvern-frontend/).