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/lucifermornens/kontext-engine/agents-mdgit clone --depth 1 https://github.com/LuciferMornens/kontext-engineWrote 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/lucifermornens/kontext-engine/agents-md)<a href="https://agentmods.dev/instructions/lucifermornens/kontext-engine/agents-md"><img src="https://agentmods.dev/badge/instructions/lucifermornens/kontext-engine/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.00889 | $0.00889 |
| Opus 5 | $0.00445 | $0.00445 |
| Sonnet 5 | $0.00178 | $0.00178 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
kontext-engine 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 6d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
North star
Ship small, modular, production-ready changes with high-signal context and tests that gate progress. Correctness > speed.
Commands (keep updated)
Put real, copy-pastable commands here. If missing, discover them in
README.md,package.jsonscripts,Makefile, or.github/workflows/*.
- Install deps:
npm install - Lint:
npm run lint - Typecheck:
npm run typecheck - Unit tests:
npm run test - Integration/E2E tests:
npm run test - Full local check (closest to CI):
npm run check
1) Context engineering (mandatory before acting)
Before editing anything, gather and organize only the context needed to execute correctly.
Before starting any task
- Understand scope
- Read the relevant existing files first (don’t guess).
- Identify existing patterns/utilities/conventions to follow.
- Note dependencies and potential side effects.
- Gather context
- Which files/modules will be affected?
- What existing code should be referenced or reused?
- Are there similar implementations to mirror?
- Plan the approach
- Break work into discrete, verifiable steps.
- Call out risks/failure points and how you’ll detect them.
- Maintain focus
- Keep working memory limited to task-relevant facts.
- For long tasks: periodically summarize “what changed / what’s next”.
- Record decisions that affect future work (short comments, docs, or ADR).
If requirements are unclear: ask a targeted question or propose a short plan—don’t invent requirements.
2) Modular architecture (default posture)
- Prefer small, composable modules with single responsibility.
- Keep boundaries explicit: clear public interfaces, minimal coupling.
- Reuse existing utilities and patterns; avoid duplicating logic.
- Localize change: avoid drive-by refactors unless required for correctness.
- Prefer dependency direction that keeps core logic independent of frameworks/UI/IO.
3) Production-ready quality (no leftovers)
No “almost done” code. No shortcuts.
- 🚫 No
TODO,FIXME, “temporary” hacks, commented-out blocks, dead code. - 🚫 No debug logs/noisy prints left behind.
- Handle errors and edge cases; validate inputs; preserve backward compatibility unless explicitly changing it.
- Keep code readable: good names, small functions, consistent style, strict types where applicable.
- Update docs/examples when behavior or APIs change.
- Never introduce or leak secrets/PII; avoid logging sensitive data.
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.
- 6d ago First seen · 93 lines · 889 tokens per session scan A 54cec3d1afc3
kontext-engine AGENTS.md is an instructions file published in the GitHub repository LuciferMornens/kontext-engine (23 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 889 tokens to every session, about $0.0044 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
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).
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 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.
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.