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 commands/hyperb1iss/moonrepo-skill/moon-rungit clone --depth 1 https://github.com/hyperb1iss/moonrepo-skillWrote 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/commands/hyperb1iss/moonrepo-skill/moon-run)<a href="https://agentmods.dev/commands/hyperb1iss/moonrepo-skill/moon-run"><img src="https://agentmods.dev/badge/commands/hyperb1iss/moonrepo-skill/moon-run.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.00020 | $0.00352 |
| Opus 5 | $0.00010 | $0.00176 |
| Sonnet 5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
moon-run 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.
What it actually says
Run Moon Tasks
Execute moon tasks with appropriate flags based on context.
Target Syntax
| Pattern | Description |
|---|---|
project:task |
Specific project and task |
:task |
All projects with this task |
#tag:task |
Projects with tag (quote in shell) |
^:task |
Upstream dependencies |
Common Patterns
Run Single Task
moon run {{target}}
Run with Affected Detection
moon run {{target}} --affected
Run in CI Mode
moon ci {{target}}
Force Bypass Cache
moon run {{target}} --force
Pass Arguments to Command
moon run {{target}} -- --coverage --verbose
Run with MQL Filter
moon run :build --query "language=typescript"
Interactive Selection
If no target provided:
moon run --interactive
Execution
- If target provided, run
moon run {{target}} - If CI environment detected, suggest
moon ciinstead - For local development, suggest
--affectedfor faster iteration - Report execution results and any cached tasks
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 · 75 lines · 20 tokens per session scan A b11a963680b3
moon-run is a command published in the GitHub repository hyperb1iss/moonrepo-skill (5 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 352 once invoked, about $0.0001 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 commands, from other repositories
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
cf-scaffold-project
Scaffold a Cloudflare project — Worker, Pages, or Worker+D1+R2 starter — with Wrangler config, Terraform skeleton, and GitHub Actions deploy using scoped API tokens.