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/navikt/copilot/copilot-instructionsgit clone --depth 1 https://github.com/navikt/copilotWrote 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/navikt/copilot/copilot-instructions)<a href="https://agentmods.dev/instructions/navikt/copilot/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/navikt/copilot/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 | $0.03922 | $0.03922 |
| Opus 5 | $0.01961 | $0.01961 |
| Sonnet 5 | $0.00784 | $0.00784 |
| Haiku 4.5 | $0.00392 | $0.00392 |
Grade A, and why
copilot 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 today.
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 — 483 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for navikt/copilot
Repository Overview
Monorepo containing Nav's GitHub Copilot ecosystem tools:
- my-copilot - Self-service portal for managing Copilot subscriptions (Next.js 16)
- copilot-api - Backend API for Copilot data and seat management (Go)
- copilot-metrics - Naisjob that populates BigQuery with daily Copilot usage metrics (Go)
- mcp-onboarding - Reference MCP server with GitHub OAuth (Go)
- mcp-registry - Public registry for Nav-approved MCP servers (Go)
All applications deployed on NAIS platform with environment-specific configurations.
Security architecture: See SECURITY.md for trust zones, auth flow, and secret isolation.
Nav Development Standards
These standards apply across Nav projects. Project-specific guidelines follow below.
Nav Principles
- Team First: Autonomous teams with circles of autonomy, supported by Architecture Advice Process
- Product Development: Continuous development and product-organized reuse over ad hoc approaches
- Essential Complexity: Focus on essential complexity, avoid accidental complexity
- DORA Metrics: Measure and improve team performance using DevOps Research and Assessment metrics
Nav Tech Stack
- Backend: Kotlin with Ktor, PostgreSQL, Apache Kafka
- Frontend: Next.js 16+, React, TypeScript, Aksel Design System
- Platform: Nais (Kubernetes on Google Cloud Platform)
- Auth: Azure AD, TokenX, ID-porten, Maskinporten
- Observability: Prometheus, Grafana Loki, Tempo (OpenTelemetry)
Nav Code Standards
Minimal Editing
When fixing a bug or implementing a feature, change only what is necessary. Do not rename variables, restructure working code, or refactor beyond the task at hand. Keep diffs small and focused so they are easy to review.
Kotlin/Ktor Patterns
- ApplicationBuilder pattern for bootstrapping
- Sealed classes for environment configuration (Dev/Prod/Local)
- Kotliquery with HikariCP for database access
- Rapids & Rivers pattern for Kafka event handling
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.
- today Changed · +11 lines · +153 tokens per session 53d80cd88245
- 4d ago First seen · 472 lines · 3,769 tokens per session scan A 9b76cfe5eb04
copilot copilot-instructions.md is an instructions file published in the GitHub repository navikt/copilot (54 stars, last pushed today), licensed MIT. It adds 3,922 tokens to every session, about $0.0196 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
sensei AGENTS.md
Instructions for spboyer/sensei, covering agents.md, repository structure, key conventions, skill.md format and skill body (markdown).
sensei copilot-instructions.md
Instructions for spboyer/sensei, covering copilot instructions, project context, skill authoring rules, token and scoring expectations and validation commands.
SonarCloud-Skill-Agent-Guidance
Repository guidance for the SonarCloud/SonarQube findings management skill.
kasetto CLAUDE.md
Claude Code instructions for pivoshenko/kasetto, covering claude.md, what this repo is, commands, rust architecture and module map.
Copilot-Skills copilot-instructions.md
Copilot instructions for TheSethRose/Copilot-Skills, covering copilot instructions, find what you're looking for, get file context before editing, understand related code and orchestration default.
Copilot-Skills document-project.instructions.md
Auto-loaded guidance for generating project documentation across any codebase.