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/pedromosquera/squadai/copilot-instructionsgit clone --depth 1 https://github.com/PedroMosquera/squadaiWrote 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/pedromosquera/squadai/copilot-instructions)<a href="https://agentmods.dev/instructions/pedromosquera/squadai/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/pedromosquera/squadai/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.00273 | $0.00273 |
| Opus 5 | $0.00137 | $0.00137 |
| Sonnet 5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade C, and why
squadai 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 5d 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.
<!-- squadai:copilot-instructions --> What it actually says
Team Standards
Project: squadai
Stack: Go
General Principles
- Follow existing patterns in the codebase. Consistency matters more than personal preference.
- Make minimal, focused changes. Avoid unrelated modifications in the same changeset.
- Every change should be reviewable: clear purpose, limited scope, easy to verify.
Verification Commands
- Tests:
go test ./... - Build:
go build ./... - Lint:
go vet ./...
Code Style
- Follow existing patterns in the codebase
- Write tests for new functionality
- Use clear, descriptive naming
- Keep functions focused on a single responsibility
- Remove dead code and unused imports
Error Handling
- Handle errors explicitly. Never silently ignore failures.
- Provide descriptive error messages with context for debugging.
- Validate inputs at system boundaries.
Commit Messages
- Use conventional commit format (feat:, fix:, docs:, test:, refactor:)
- Keep the first line under 72 characters
- Explain why the change was made, not just what changed
Architecture
- Respect package boundaries and import rules
- Keep domain logic free of infrastructure concerns
- All mutating operations must support dry-run mode
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.
- 5d ago First seen · 45 lines · 273 tokens per session scan C 610324afbf89
squadai copilot-instructions.md is an instructions file published in the GitHub repository PedroMosquera/squadai (8 stars, last pushed 1mo ago), licensed MIT. It adds 273 tokens to every session, about $0.0014 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-31.
Other instructions, from other repositories
dingtalk-workspace-cli AGENTS.md
AGENTS.md instructions for DingTalk-Real-AI/dingtalk-workspace-cli, covering repository agent guide, build and test, command framework declaration, flag / help / schema homology and agent schema contract.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.
agentic-playwright enums.instructions.md
Instructions for idavidov13/agentic-playwright, covering enums, critical, file locations, instructions and phase 1: decide if the value belongs in an enum.
unraid-management-agent copilot-instructions.md
Copilot instructions for ruaan-deysel/unraid-management-agent, covering copilot instructions, copilot workflow, path-specific instructions, reusable prompts and quick commands.
coral CLAUDE.md
Instructions for cdknorow/coral, covering claude.md - coral go, mission, testing, go unit tests and legacy parity tools (historical reference).
free-ai-gateway AGENTS.md
Instructions for zaber-dev/free-ai-gateway, covering 🤖 free-ai gateway - agentic development guidelines, 🏛️ monorepo architecture & package boundaries, 🛑 strict architectural rules for agents, 💻 essential developer commands and build all packages across monorepo.