Borrowing it
Nothing to install: this file belongs to ThiagoGuislotti/copilot-instructions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ThiagoGuislotti/copilot-instructions/main/.github/instructions/observability-sre.instructions.mdgit clone --depth 1 https://github.com/ThiagoGuislotti/copilot-instructionsWrote 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/thiagoguislotti/copilot-instructions/observability-sre)<a href="https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/observability-sre"><img src="https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/observability-sre.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.00603 | $0.00603 |
| Opus 5 | $0.00302 | $0.00302 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
copilot-instructions observability-sre.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 7d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability and SRE Baseline
- Use this instruction when designing runtime telemetry, reliability operations, incident response, and service-level objectives.
- Treat observability as a product requirement; every critical user flow must be measurable end-to-end.
SLO and Error Budget
- Define SLI and SLO per critical journey using explicit targets for availability, latency, and correctness.
- Track error budget consumption and use it to gate release risk and change velocity.
- Prefer a small set of business-aligned SLOs over large metric catalogs with low actionability.
Telemetry Design
- Adopt OpenTelemetry standards for traces, metrics, and logs across services and async boundaries.
- Propagate correlation identifiers and trace context through HTTP, messaging, jobs, and batch pipelines.
- Emit structured logs with stable fields and severity semantics; avoid free-text only logging.
- Ensure every metric has clear unit, owner, and operational purpose.
Metrics Quality
- Instrument golden signals first: latency, traffic, errors, saturation.
- Control cardinality for labels and dimensions to avoid storage and query cost explosions.
- Prefer histograms and percentile-friendly metrics for latency objectives.
- Separate technical metrics from product metrics and connect both through shared context fields.
Alerting and Incident Response
- Use multi-window, multi-burn-rate alerting for SLO-backed incidents.
- Configure alerts to be actionable with runbook links, ownership, and expected first response.
- Avoid noisy threshold-only alerts without clear incident semantics.
- Define incident severity levels, communication channels, escalation paths, and handoff protocol.
Dashboard and Runbook Standards
- Maintain service dashboards with request rates, error rates, percentile latencies, dependency health, and resource saturation.
- Keep runbooks versioned with deterministic diagnosis and mitigation steps.
- Include rollback strategy, feature-flag strategy, and verification checklist in runbooks.
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.
- 7d ago First seen · 56 lines · 603 tokens per session scan A 400d940faa19
copilot-instructions observability-sre.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 2mo ago), licensed MIT. It adds 603 tokens to every session, about $0.0030 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
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).
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.
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.
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).
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.