copilot-instructions microservices-performance.instructions.md

copilot-instructions microservices-performance.instructions.md is an instructions file for GitHub Copilot from ThiagoGuislotti/copilot-instructions. It costs 972 tokens per session, scanned A, original, MIT.

A set of design and coding rules for systems split into several independent services, called microservices. It covers service boundaries, communication, performance, resource use, and data consistency.

In plain words
What is it for?
Use it when designing or reviewing microservice boundaries, APIs, message-based communication, caching, database access, containers, and service reliability.
Why use it?
It gives an agent consistent guidance for avoiding poorly separated services, slow operations, wasted resources, and failures when services communicate.

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/thiagoguislotti/copilot-instructions/microservices-performance
Clone the repo
git clone --depth 1 https://github.com/ThiagoGuislotti/copilot-instructions

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for copilot-instructions microservices-performance.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/microservices-performance.svg)](https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/microservices-performance)
Your own site
<a href="https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/microservices-performance"><img src="https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/microservices-performance.svg" alt="Measured on agentmods" height="20"></a>
Per session 972 This file is loaded in full into every session.
When invoked 972 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.00972 $0.00972
Opus 5 $0.00486 $0.00486
Sonnet 5 $0.00194 $0.00194
Haiku 4.5 $0.00097 $0.00097

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

Security

Grade A, and why

copilot-instructions microservices-performance.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.

.github/instructions/microservices-performance.instructions.md · 217 lines

How it starts

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

Service boundaries

  • Single responsibility
  • Domain-driven boundaries
  • Database per service
  • Prefer async communication
  • Event-driven architecture
  • Saga for distributed transactions
  • API gateway as entry point
routes:
  - path: /orders
    service: order-service

Performance

  • Configured connection pooling
  • Consistent async/await
  • Bulk operations
  • Appropriate lazy loading
  • Distributed cache (Redis)
  • CDN for assets
  • Compression enabled
var cache = ConnectionMultiplexer.Connect("redis");
cache.GetDatabase().StringSet("key", value);

Resource efficiency

  • Minimal images
  • Multi-stage builds
  • Defined resource limits
  • Accurate CPU/memory requests
  • HPA/VPA
  • Tuned probes
resources:
  limits:
    cpu: "500m"
    memory: "512Mi"
  requests:
    cpu: "250m"
    memory: "256Mi"

Communication

  • gRPC for service-to-service
  • REST for external APIs
  • Message queues for async
  • Circuit breaker
  • Retries with exponential backoff
  • Timeouts
  • Idempotent operations
.AddPolicyHandler(Policy.Handle<Exception>().WaitAndRetryAsync(3, retry => TimeSpan.FromSeconds(Math.Pow(2, retry))))

Consistency

  • Eventual consistency by default
  • CQRS when applicable
  • Event sourcing for audit
  • Saga orchestration
  • Compensation patterns
  • Avoid distributed transactions
  • Optimized read models
public class OrderSaga { /* Orchestrate steps with compensation */ }

Caching

  • Application cache
  • Distributed cache
  • Cache-aside
  • Write-through when needed
  • Proper TTL
  • Invalidation
  • Warming
  • Hierarchy
var value = cache.Get("key") ?? LoadAndCache("key");

Load balancing

  • Round-robin default
  • Health-based routing
  • Session affinity when needed
  • Geo routing
  • A/B testing
  • Canary
  • Blue-green
spec:
  template:
    metadata:
      labels:
        version: v2
  traffic: 10%

Monitoring

  • Structured logs
  • Correlation IDs
  • Metrics aggregation
  • Tracing
  • SLA monitoring
  • Error rate
  • Latency percentiles
  • Resource utilization
- job_name: 'service'
  metrics_path: /metrics

Read the full file on GitHub · 217 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. 3d ago First seen · 217 lines · 972 tokens per session scan A 03329dbe824d

Subscribe to this mod's changes

copilot-instructions microservices-performance.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 2mo ago), licensed MIT. It adds 972 tokens to every session, about $0.0049 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.

Related

Other instructions, from other repositories

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens