Borrowing it
Nothing to install: this file belongs to gszr/lunar. 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/gszr/lunar/main/AGENTS.mdgit clone --depth 1 https://github.com/gszr/lunarWrote 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/gszr/lunar/agents-md)<a href="https://agentmods.dev/instructions/gszr/lunar/agents-md"><img src="https://agentmods.dev/badge/instructions/gszr/lunar/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/gszr/lunar/agents-md"><img src="https://agentmods.dev/badge/instructions/gszr/lunar/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01068 | $0.01068 |
| Opus 5.5 | $0.00427 | $0.00427 |
| Sonnet 5.5 | $0.00214 | $0.00214 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
lunar 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 22d 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.
How to work here
Lunar is a small Rust host with a Lua guest. Keep it that way.
Our goals
- We are a barebones coding harness.
- We aim at transparency context efficiency: no hidden system prompts that waste tokens and confuse the LLM.
Before you type
- Read
CONTEXT.md. Locked decisions stay locked. If something is unclear, ask. - Look at the code — and at Pi when the behavior is “like Pi” — before asking. If the tree answers it, do not ask.
- Unsettled product shape: ask one question, recommend an answer, wait.
- Once the shape is agreed, or the user says implement, stop asking and ship a small slice. Iterate later.
Code
- Simplest thing that works. No speculative abstraction, no “for later” types, no unused flags.
- Small modules, small surface. Split a file before it becomes a junk drawer.
mainstays a thin entry. - Match the code that is already here. Same names, same patterns, same density.
- Precise names from the domain.
/missionnot/session. Do not invent vocabulary. - Do not add workflow to the binary. Do not mix the Lua config path with the env path.
Scope
- Smallest useful diff for this request. One vertical slice you can run.
- Do not “improve” nearby code, comments, or formatting.
- Do not touch unrelated files. Leave workflow, generated, and personal files alone.
Check your work
- Investigate yourself. Do not ask the user to run something you can run.
- Prefer a real run over a mock. If it fails, find the root cause.
- Add a test only when it protects a behavior that could break. No tests that only prove a library works.
- When a product decision changes, update
CONTEXT.mdin the same turn. Keep the README short enough to start.
Git
- Commit only when asked.
- Conventional commits (
feat:,fix:,docs:,refactor:). - Separate commits for separate concerns.
- Run
cargo fmt --checkandcargo clippyand fix issues before committing.
Changelog
- You always update the changelog for user-facing feature, not internal changes like CI and automation, describing the change in user-facing terms, not implementation details
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.
- 22d ago Changed · +42 lines · +565 tokens per session 9aae7278e058
- 24d ago Changed · +6 lines · +44 tokens per session fd54238de7e4
- 1mo ago First seen · 45 lines · 459 tokens per session scan A 5e60cfd98f32
lunar AGENTS.md is an instructions file published in the GitHub repository gszr/lunar (17 stars, last pushed 4d ago), licensed MIT. It adds 1,068 tokens to every session, about $0.0043 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).