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 skills add xonovex/platform --skill moon-guidegit clone --depth 1 https://github.com/xonovex/platformWrote 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/skills/xonovex/platform/moon-guide)<a href="https://agentmods.dev/skills/xonovex/platform/moon-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/moon-guide/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/skills/xonovex/platform/moon-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/moon-guide.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.00060 | $0.00798 |
| Opus 5.5 | $0.00024 | $0.00319 |
| Sonnet 5.5 | $0.00012 | $0.00160 |
| Haiku 4.5 | $0.00006 | $0.00080 |
Grade A, and why
moon-guide 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Moon Build System Guidelines
Define reusable Moon tasks through tags, explicit dependencies, and declared cache inputs and outputs.
Requirements
- Moon ≥ 2.0, Node.js for JavaScript/TypeScript projects.
- Migration from v1: Run
moon migrate v2to automate configuration updates.
Essentials
- Task configuration - Define in
.moon/tasks/*.ymlfor auto-inheritance, see references/task-configuration.md, references/task-inheritance.md - Tags - Use for categorization, filtering, boundaries, inheritance, see references/tag-based-filtering.md
- Execution -
project:task,#tag:task,:task(all),--query,--affected - Querying - Query projects/tasks by tags, language, or query language, see references/query-language.md
- Configuration - Projects use
moon.yml, workspace uses.moon/workspace.yml - Toolchains - Moon manages language toolchains, configured in
.moon/toolchains.yml(plural in v2) - Caching - Built-in task caching with output definitions, see references/task-configuration.md
Moon 2.0 Key Changes
- command vs script - Use
script:for shell features (pipes, redirects, chaining);command:for simple executables only - Shell by default - Tasks run in shell by default (
bashon Unix,pwshon Windows) - Deep merging - Configs merge sequentially (not shallow), fileGroups combine instead of replace
- Renamed settings -
platform→toolchains,type→layer,toolchain.yml→toolchains.yml - Env var syntax -
$VARsubstitutes empty string (not syntax fallback); use${VAR:-default}for defaults
Gotchas
- Task inheritance flows from
.moon/tasks/*.yml(by tag/language) → projectmoon.yml: overriding requires the same task key in the project file - Implicit task dependencies via
deps:are project-scoped: cross-project deps need<project>:<task>syntax moon ciskips persistent server tasks (preset: 'server') and any task withoptions.runInCI: false, never gate CI-only checks behind a non-CI task- Project tags drive task inheritance; misspelling a tag silently disables the inherited tasks for that project
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- eval-queries.json 5.2 KB
- evals.json 2.2 KB
- moon.yml 166 B
- references/docker-multistage.md 961 B
- references/migration-v2.md 3.0 KB
- references/project-constraints.md 927 B
- references/query-language.md 1.2 KB
- references/tag-based-filtering.md 1.2 KB
- references/task-configuration.md 1.8 KB
- references/task-inheritance.md 1.7 KB
- SOURCES.md 578 B
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 Changed · +2 lines ed24c00da879
- 1mo ago First seen · 47 lines · 60 tokens per session scan A b398461b083b
moon-guide is a skill published in the GitHub repository xonovex/platform (6 stars, last pushed 5d ago), licensed MIT. It adds 60 tokens to every session and 798 once invoked, about $0.0002 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-09-08.
Other skills, from other repositories
harbor-daytona
Use Harbor's Daytona sandbox platform for computer use — creating sandboxes, taking screenshots, sending mouse/keyboard input, and building agent loops. Use when the user wants to interact with a GUI, automate a desktop, do computer use, control a browser visually, or run Claude computer use against a Daytona sandbox.
docker
Use when authoring or auditing a Dockerfile, shrinking a bloated image, hardening a container that runs as root, picking a base image, or wiring a Compose dev loop with hot reload. NOT CI builds or deploy-to-host (that is deployment), NOT k8s autoscaling (that is scaling), NOT app-level injection or secrets-in-code…
kastell
Server security auditing, hardening, and fleet management. 457 security checks across 30 categories (SSH, Firewall, Docker, TLS, HTTP Headers), CIS/PCI-DSS/HIPAA compliance mapping, 24-step production hardening, and 13 MCP tools. Supports Hetzner, DigitalOcean, Vultr, and Linode with Coolify, Dokploy, and bare VPS…
ilo
Run builds, tests, and other tooling inside a reproducible, containerized dev environment via the ilo CLI instead of on the host. Use this whenever a project relies on ilo, devcontainers, or container-based build environments — it has a .ilo.rc / .ilo/ilo.rc, dev/ argument files, a Containerfile/Dockerfile, a…
docker-compose-local-setup
Creates or updates local multi-service orchestration using docker compose. Covers compose.yaml design, service health checks, dependson readiness, env files, named volumes, migrations/seeds jobs, verification commands, and cleanup workflows for local development.
compose
A guide to Docker Compose, a tool for defining and running applications made of multiple containers, such as a web app, API, and database.