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/basher83/lunar-claude/agents-mdgit clone --depth 1 https://github.com/basher83/lunar-claudeWrote 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/basher83/lunar-claude/agents-md)<a href="https://agentmods.dev/instructions/basher83/lunar-claude/agents-md"><img src="https://agentmods.dev/badge/instructions/basher83/lunar-claude/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.00625 | $0.00625 |
| Opus 5 | $0.00313 | $0.00313 |
| Sonnet 5 | $0.00125 | $0.00125 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
lunar-claude 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 5d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This file provides guidance to agents when working with code in this repository.
Project Overview
lunar-claude is a personal Claude Code plugin marketplace for homelab and infrastructure automation. It provides reusable AI-powered tools organized into a structured plugin ecosystem.
Plugin Categories:
meta/- Tools for creating Claude Code componentsinfrastructure/- Infrastructure as Code tools (Terraform, Ansible, Proxmox)devops/- Container orchestration and DevOps tools (Kubernetes, Docker)homelab/- Homelab-specific utilities (NetBox, PowerDNS)personal/- Personal workstation operations (macOS diagnostics, RCA)
Commands
# Environment setup
mise install # Install all tools (Python, ruff, uv, etc.)
uv sync --group dev # Install Python dependencies
mise run hooks-install # Install pre-commit + infisical hooks
# Code quality
ruff check . # Lint Python
ruff format . # Format Python
pyright # Type check (strict mode)
mise run pre-commit-run # Run all pre-commit hooks
# Testing
pytest tests/ # Run all tests
pytest tests/test_verify_structure.py # Run single test file
# Validation
./scripts/verify-structure.py # Validate plugin/marketplace structure
mise run markdown-lint # Lint markdown (rumdl)
mise run link-check # Check links in markdown (lychee)
# Changelog
mise run changelog # Update CHANGELOG.md
mise run changelog-bump <version> # Release with version bump
Code Quality
- Python >=3.13 managed via mise + uv
- Formatter/Linter: ruff (config in
ruff.toml) - Type checker: pyright strict mode (
pyrightconfig.json) - Standalone scripts: Use PEP 723 inline metadata with
#!/usr/bin/env -S uv run
Claude Tools
Use the Skill tool to load pre-built agent skills (can load multiple at once).
Use SlashCommand to execute custom slash commands programmatically.
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.
- 5d ago First seen · 77 lines · 625 tokens per session scan A 1cb27651c9aa
lunar-claude AGENTS.md is an instructions file published in the GitHub repository basher83/lunar-claude (22 stars, last pushed today), licensed MIT. It adds 625 tokens to every session, about $0.0031 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
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).
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.
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).