Borrowing it
Nothing to install: this file belongs to Starefossen/NisseKomm. 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/Starefossen/NisseKomm/main/AGENTS.mdgit clone --depth 1 https://github.com/Starefossen/NisseKommWrote 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/starefossen/nissekomm/agents-md)<a href="https://agentmods.dev/instructions/starefossen/nissekomm/agents-md"><img src="https://agentmods.dev/badge/instructions/starefossen/nissekomm/agents-md.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.02776 | $0.02776 |
| Opus 5 | $0.01388 | $0.01388 |
| Sonnet 5 | $0.00555 | $0.00555 |
| Haiku 4.5 | $0.00278 | $0.00278 |
Grade A, and why
NisseKomm AGENTS.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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NisseKomm - Development Guide for AI Agents
Important: Keep this document updated when making changes to the project. Always run
pnpm checkat the end of coding sessions to verify code quality. Assume the dev server is already running at http://localhost:3000.Do NOT create new markdown files (like SUMMARY.md, CHANGES.md, etc.) to document your work unless explicitly requested by the user.
Quick Navigation
Session Starter (you're here): Project essence, critical patterns, environment setup Deep Dive References:
- 📐 ARCHITECTURE.md - Layout patterns, module system, state management, date handling
- 🎮 IMPLEMENTATION.md - Game mechanics, user flows, component behaviors
- 🎨 DESIGN_SYSTEM.md - Visual design, colors, animations, responsive patterns
- ✍️ CONTENT_GUIDE.md - Norwegian vocabulary, character voices, puzzle design
Project Overview
NisseKomm is an advent calendar experience for children (ages 9-12) that bridges the physical and digital worlds. Rampenissen, the silly but friendly elf stationed with the kids, needs their help on a mission from Julius (Santa). Kids solve daily riddles by finding clues in both the real world and inside NisseKomm - the digital headquarters for critical Snøfall operations.
Core Experience: Rampenissen's daily emails → scavenge for physical clues → access digital HQ → combine hints from both worlds → solve riddles → unlock Julius' secrets.
The Physical-Digital Bridge: This is NOT a purely digital game. Success requires exploring BOTH worlds - searching the house for physical clues while investigating files in NisseKomm's retro CRT terminal. The two worlds intertwine throughout December 1-24.
Universe: Based on Snøfall TV series - Julius (Santa) in magical Snøfall with Nissemor and elves. Rampenissen does humorous mischiefs during advent while keeping a watchful eye on the kids, but this year he needs their problem-solving help.
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 · 288 lines · 2,776 tokens per session scan A 9bf5a0bd9380
NisseKomm AGENTS.md is an instructions file published in the GitHub repository Starefossen/NisseKomm (5 stars, last pushed 8mo ago), licensed MIT. It adds 2,776 tokens to every session, about $0.0139 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.