agent-plugins copilot-instructions.md

Coding instructions for Agent Plugins for AWS, a collection of extensions that help coding agents work with Amazon Web Services. They describe the TypeScript stack, plugin layout, infrastructure tools, and checks for code quality and leaked secrets.

In plain words
What is it for?
Use them when adding or modifying AWS plugin features, schemas, tools, infrastructure-as-code support, documentation, or automated checks.
Why use it?
They provide the project context and contribution rules needed to change plugins without breaking its structure or bypassing security checks.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/awslabs/agent-plugins/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/awslabs/agent-plugins

Made for: GitHub Copilot.

Per session 586 This file is loaded in full into every session.
When invoked 586 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00586 $0.00586
Opus 5 $0.00293 $0.00293
Sonnet 5 $0.00117 $0.00117
Haiku 4.5 $0.00059 $0.00059

Measured 2d ago against content hash adf8ec767e64, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-plugins 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 2d 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.

.github/copilot-instructions.md · 58 lines

How it starts

The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Copilot Custom Instructions for Agent Plugins for AWS

Project Overview

This repository contains Agent Plugins for AWS that equip AI coding agents with the skills to help architects, deploy, and operate on AWS. Plugins include deploy-on-aws (recommendations, cost estimates, and Infrastructure as Code generation) and amazon-location-service (maps, geocoding, routing, and geospatial features).

Technology Stack

  • Language: Primarily TypeScript/JavaScript
  • Framework: Claude Code plugins
  • Cloud Platform: AWS
  • Infrastructure as Code: CDK and CloudFormation
  • Tools: MCP Servers (awsknowledge, awspricing, aws-iac-mcp)

Code Organization

  • /plugins - Plugin implementations
  • /schemas - Data schemas and type definitions
  • /tools - Utility tools and helpers
  • /.github - GitHub workflows and configuration
  • Root files: Configuration for linting (markdownlint, semgrep), security (gitleaks), and formatting (dprint)

Development Practices

  1. Code Quality: Uses pre-commit hooks, semgrep for security analysis, and gitleaks for secret detection
  2. Documentation: Comprehensive guides including DEVELOPMENT_GUIDE.md, CONTRIBUTING.md, TROUBLESHOOTING.md
  3. Testing: Follow existing test patterns in the codebase
  4. Formatting: Use dprint for code formatting consistency
  5. Commit Signoff: Web commit signoff required (git commit -S flag)

Plugin Development Guidelines

  • Follow the workflow pattern: Analyze → Recommend → Estimate → Generate → Deploy
  • MCP Servers provide: AWS documentation, pricing data, and IaC best practices
  • Skill triggers should be intuitive natural language phrases users would say
  • Always include cost estimation and confirmation steps before deployment
  • Generate infrastructure code with explanations and best practices

Important Reminders for Copilot

  1. AWS Best Practices: Recommend services aligned with AWS Well-Architected Framework
  2. Cost Awareness: Always estimate and display costs to users
  3. User Confirmation: Never deploy without explicit user confirmation
  4. Multi-Agent Support: Currently supports Claude Code; consider extensibility
  5. Security: Follow AWS security best practices and principle of least privilege
  6. Documentation: Provide clear explanations for architectural recommendations

Read the full file on GitHub · 58 lines

Changes

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.

  1. 2d ago First seen · 58 lines · 586 tokens per session scan A adf8ec767e64

Subscribe to this mod's changes

agent-plugins copilot-instructions.md is an instructions file published in the GitHub repository awslabs/agent-plugins (876 stars, last pushed 6d ago), licensed Apache-2.0. It adds 586 tokens to every session, about $0.0029 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.