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.
git clone --depth 1 https://github.com/shuchitajain/awesome-ai-setupWrote 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/shuchitajain/awesome-ai-setup/copilot-instructions)<a href="https://agentmods.dev/instructions/shuchitajain/awesome-ai-setup/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/shuchitajain/awesome-ai-setup/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.01020 | $0.01020 |
| Opus 5 | $0.00510 | $0.00510 |
| Sonnet 5 | $0.00204 | $0.00204 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade A, and why
awesome-ai-setup 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Instructions
These instructions apply to this Flutter project for all AI coding assistance.
Tech Stack
- Flutter 3.x with Dart 3.x (null safety, records, sealed classes, patterns)
- Riverpod 2.x with
riverpod_annotationand code generation - GoRouter for navigation
- Freezed for immutable state classes and value objects
- flutter_hooks for local widget state (used via
HookConsumerWidget) - dio for HTTP with custom interceptors
- Hive for local data caching
- Firebase (Auth, Firestore, Storage, Messaging) for backend
Architecture
Feature-first Clean Architecture with three layers per feature:
data/- repository implementations, data sources, JSON modelsdomain/- entities, repository interfaces, use cases (pure Dart, no Flutter)presentation/- screens, widgets, Riverpod providers
All new features go under lib/features/[feature_name]/. See ARCHITECTURE.md for the full structure.
Rules
Widgets
- Default base class is
HookConsumerWidget- use it unless the widget is a pure display component with no state or providers - Use
StatelessWidgetonly for widgets that receive all data as parameters and have no side effects - Do not use
StatefulWidget. Do not useConsumerWidget. Do not useHookWidget - Widget file names:
snake_case.dart. Widget class names:PascalCase - All user-facing strings go through
AppLocalizations- no hardcoded strings in UI
State management
- All state management is Riverpod - do not use
setState,ValueNotifier,ChangeNotifier,InheritedWidget, or theproviderpackage - Async state uses
AsyncNotifier- sync state usesNotifier - State classes use
@freezed- no manual==/hashCode/copyWith ref.watchin build,ref.readin callbacks - neverref.readinsidebuild()
Navigation
- All navigation through GoRouter:
context.go(),context.push(),context.pop() - Route name constants live in
core/router/routes.dart - Do not use
Navigator.push/pop/pushNameddirectly
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 · 125 lines · 1,020 tokens per session scan A 71ef15701ce1
awesome-ai-setup copilot-instructions.md is an instructions file published in the GitHub repository shuchitajain/awesome-ai-setup (5 stars, last pushed 3mo ago), licensed MIT. It adds 1,020 tokens to every session, about $0.0051 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.