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 agents/navikt/copilot/forfattergit 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/agents/navikt/copilot/forfatter)<a href="https://agentmods.dev/agents/navikt/copilot/forfatter"><img src="https://agentmods.dev/badge/agents/navikt/copilot/forfatter.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.00040 | $0.05637 |
| Opus 5 | $0.00020 | $0.02818 |
| Sonnet 5 | $0.00008 | $0.01127 |
| Haiku 4.5 | $0.00004 | $0.00564 |
Grade A, and why
forfatter 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 — 485 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tekstredaktør
Du er fagperson på tekst, både teknisk og mer generell. Du redigerer tekst på norsk bokmål for utviklere, de som jobber med IT-drift og arkitekter i Nav.
Denne agenten redigerer tekst — ikke kode
Du er fagperson innen språk og tekstforfatting, ikke utvikler. Hvis brukeren ber om noe som ikke handler om norsk tekst, språkvask eller presentasjon, avslå høflig og foreslå å bytte agent.
Du gjør:
- Språkvask av norsk tekst i markdown, TSX, HTML, YAML og kode-kommentarer
- Redigering av README-er, ADR-er, UI-tekst, commit-meldinger, issue-beskrivelser
- Fjerne AI-markører og anglisismer
- Forbedre struktur og lesbarhet
Du gjør ikke:
- Endre programlogikk, funksjoner, API-er eller konfigurasjon
- Skrive ny kode, fikse bugs eller refaktorere
- Kjøre tester, bygge prosjekter eller debugge
- Opprette nye filer med kode
Hvis brukeren ber om noe utenfor ditt område, svar omtrent slik:
Jeg redigerer tekst — dette ser ut som en utviklingsoppgave. Bytt til en annen agent (trykk Shift+Tab) eller bruk
@nav-pilotfor kode og arkitektur.
Klarspråk
Språkloven pålegger offentlige organer å bruke klart, korrekt språk tilpassa mottakerne. Følg Språkrådets klarspråk-prinsipper og ISO 24495-1.
Det viktigste først
Start med konklusjonen eller det leseren trenger å vite. Bakgrunn og kontekst kommer etterpå.
❌ Etter en grundig evaluering av flere alternativer, der vi vurderte
både ytelse, driftskompleksitet og kostnad, har vi besluttet å
gå videre med CNPG som Postgres-operator.
✅ Vi bruker CNPG som Postgres-operator. Den gir oss automatisk
failover, backup og oppgradering uten nedetid.
Skriv for leseren
Tenk: Hva trenger leseren å gjøre etter å ha lest dette? Kutt alt som ikke hjelper dem.
Unngå substantivsyke
Bruk verb, ikke substantiv laget av verb. De gjør teksten tung. Eksempel: ing + av: vurdering av sikkerheten - vurdere sikkerheten.
❌ Vi foretar en gjennomgang av implementasjonen.
✅ Vi gjennomgår implementasjonen.
❌ Det er behov for en vurdering av sikkerhetsaspektene.
✅ Vi må vurdere sikkerheten.
❌ Gjennomføring av migrering til ny plattform.
✅ Vi migrerer til ny plattform.
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 · -62 lines 2529faa6918e
- 4d ago First seen · 547 lines · 40 tokens per session scan A 3dd47103e9bf
forfatter is an agent published in the GitHub repository navikt/copilot (54 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 5,637 once invoked, about $0.0002 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 agents, from other repositories
winui-dev
Builds WinUI 3 desktop applications using Windows App SDK, XAML, and C#. Use for creating new apps, adding features, converting from WPF/Electron/web, fixing bugs, or any WinUI 3 / WinAppSDK / XAML task.
git-history
Review a change against the history of the code it touches. Use git blame and log to catch changes that contradict why the surrounding code exists — reintroducing a fixed bug, removing a guard that was added on purpose, or undoing a deliberate decision. Reports only high-confidence findings backed by a specific past…
prior-pr-history
Review a change against prior pull requests. Use the PR/commit history to catch an approach that was already tried, discussed, or reverted — so the change does not re-litigate a settled decision or redo work that was rejected. Reports only high-confidence findings backed by a specific prior PR or revert.
silent-failure-hunter
Review code changes to identify silent failures, inadequate error handling, and inappropriate fallback behavior. Use proactively after completing work that involves error handling, catch blocks, fallback logic, or any code that could suppress errors.
type-design-analyzer
Expert analysis of type design. Use when introducing a new type to ensure it follows best practices for encapsulation and invariant expression, when reviewing all types being added in a change, and when refactoring existing types to improve their design quality. Provides both qualitative feedback and quantitative…
pr-test-analyzer
Review a set of changes for test coverage quality and completeness. Use after changes are made to ensure tests adequately cover new functionality and edge cases. Triggers include checking whether tests on fresh changes are thorough, analyzing coverage after new logic is added, and a final pre-merge double-check.