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/johnpapa/vscode-angular-snippets/copilot-instructionsgit clone --depth 1 https://github.com/johnpapa/vscode-angular-snippetsWhat 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.00641 | $0.00641 |
| Opus 5 | $0.00320 | $0.00320 |
| Sonnet 5 | $0.00128 | $0.00128 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
vscode-angular-snippets 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 3d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions — vscode-angular-snippets
Project Type
This is a VS Code snippets extension. The product is JSON snippet files — not compiled code. There is no build step, no test suite, and no runtime logic.
Snippet Conventions
Prefix naming
- All Angular snippets use the
a-prefix:a-component,a-service,a-pipe - NgRx snippets use
a-ngrx-prefix:a-ngrx-create-action,a-ngrx-create-effect - Prefixes are kebab-case, lowercase
- Keep prefixes short but descriptive
Snippet body
- Use
\tfor indentation (VS Code converts to user's tab setting) - Use
${N:default}for interactive placeholders (N starts at 1) - Use
$0for final cursor position — place it where the user will type next - Each line of the body is a separate string in the JSON array
- Follow Angular's current coding style (standalone components, functional guards)
JSON format
- Snippet files must be valid JSON — no comments, no trailing commas
- Use consistent key ordering:
prefix,description,body - Keep descriptions concise — match the style of existing snippets
Angular version alignment
- Snippets should reflect current Angular idioms (see
displayNameinpackage.jsonfor target version) - Prefer standalone components over NgModule-based components for new snippets
- Prefer functional guards (
CanActivateFn) over class-based guards - Prefer
inject()over constructor injection for new snippets
TypeScript Conventions
- The
test/directory contains placeholder tests — no active test framework - TypeScript is used only for the test harness and dev tooling, not for the extension itself
Documentation
- Every snippet must have a row in the README snippet table for its language
- Tables use the format:
| \prefix` | description |` - Group snippets by category in README (TypeScript Angular, NgRx, HTML, etc.)
Maintenance Matrix
| When this changes... | Also update... |
|---|---|
New snippet added to any snippets/*.json |
README.md (add row to the correct snippet table), CHANGELOG.md |
| New snippet file for a new language | package.json (contributes.snippets array), README.md (new table section), AGENTS.md (structure + language table) |
| Snippet prefix renamed | README.md (update the table row) |
| Snippet removed | README.md (remove the table row), CHANGELOG.md |
| Angular version bump | package.json (version, displayName, description), README.md (version references), CHANGELOG.md |
| Extension packaging/publishing | package.json (version), CHANGELOG.md, verify .vscodeignore |
| Dev container config changed | .devcontainer/devcontainer.json, .devcontainer/Dockerfile |
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.
- 3d ago First seen · 59 lines · 641 tokens per session scan A 2c096f585ccc
vscode-angular-snippets copilot-instructions.md is an instructions file published in the GitHub repository johnpapa/vscode-angular-snippets (567 stars, last pushed 4d ago), licensed MIT. It adds 641 tokens to every session, about $0.0032 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
angular AGENTS.md
Instructions for angular/angular, covering environment, key documentation, testing and pull requests.
hana-developer-cli-tool-example mcp-server-development.instructions.md
Use when creating or updating MCP (Model Context Protocol) server components. Enforces TypeScript patterns, JSON-RPC communication rules, tool/resource/prompt registration, and integration with CLI command metadata. Ensures MCP server follows protocol requirements and maintains consistency with the CLI infrastructure.
hana-developer-cli-tool-example route-development.instructions.md
Use when creating or updating route files in routes/. Enforces consistent structure, error handling, database connection management, internationalization, and integration with the Express server and CLI command infrastructure. Ensures routes follow established patterns for endpoint registration, response formatting…
hana-developer-cli-tool-example typescript-configuration.instructions.md
Use when creating or updating TypeScript configuration files. Enforces consistent compiler options, module resolution strategies, type generation from JavaScript sources, declaration file management, and dual-config patterns for mixed JS/TS projects. Ensures TypeScript integration supports both ESM and type safety…
primitives angular.instructions.md
Instructions for radix-ng/primitives, covering typescript best practices, angular best practices, components, state management and templates.
calva-backseat-driver backseat-driver-source-conventions.instructions.md
Backseat Driver extension source code conventions — Ex framework patterns, async, state management, namespace separation, and naming. Supplements universal Clojure patterns with Backseat Driver-specific rules.