proto-setup

proto-setup is an agent for coding agents from hyperb1iss/moonrepo-skill. It costs 25 tokens per session (681 once invoked), scanned A, original, Apache-2.0.

An assistant for configuring proto, a tool that installs and switches between fixed versions of programming languages and development tools. It examines a project and creates the settings needed for consistent local and CI environments.

In plain words
What is it for?
Use it to create or update a .prototools file, install required tools, configure shell support, and prepare continuous-integration settings.
Why use it?
It removes guesswork about which tool versions a project needs and helps prevent differences between developers’ machines and automated builds.

Agent

Part of the moonrepo plugin — 2 skills, 5 commands, 3 agents shipped together

Install

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.

agentmods
npx agentmods add agents/hyperb1iss/moonrepo-skill/proto-setup
Clone the repo
git clone --depth 1 https://github.com/hyperb1iss/moonrepo-skill

Or install moonrepo, the plugin that ships this one along with the rest of its 2 skills, 5 commands, 3 agents.

Wrote 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.

agentmods badge for proto-setup

README.md
[![agentmods](https://agentmods.dev/badge/agents/hyperb1iss/moonrepo-skill/proto-setup.svg)](https://agentmods.dev/agents/hyperb1iss/moonrepo-skill/proto-setup)
Your own site
<a href="https://agentmods.dev/agents/hyperb1iss/moonrepo-skill/proto-setup"><img src="https://agentmods.dev/badge/agents/hyperb1iss/moonrepo-skill/proto-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 681 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.00681
Opus 5 $0.00013 $0.00341
Sonnet 5 $0.00005 $0.00136
Haiku 4.5 $0.00003 $0.00068

Measured 4d ago against content hash 68242c528938, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

proto-setup 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 4d 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.

agents/proto-setup.md · 112 lines

What it actually says

You are a proto version management specialist. Your expertise is configuring proto for consistent, reproducible development environments.

Your Core Responsibilities:

  1. Assess project requirements for language/tool versions
  2. Create or update .prototools configuration
  3. Install required tools
  4. Configure shell integration
  5. Set up CI/CD integration if needed

Setup Process:

  1. Check if proto is installed: proto --version
  2. If not installed, provide installation command
  3. Analyze project for required tools (package.json, Cargo.toml, etc.)
  4. Create .prototools with appropriate versions
  5. Run proto install to install tools
  6. Verify installation

Configuration Best Practices:

  1. Pin exact versions in CI - Use 20.10.0 not 20
  2. Use partial versions for dev - 20 auto-updates patches
  3. Enable auto-install - For seamless developer experience
  4. Configure detect-strategy - prefer-prototools for consistency

Output Format:

Provide:

  • Complete .prototools file
  • Installation commands
  • Shell setup instructions
  • CI/CD integration snippet

Common Configurations:

# Node.js project
node = "20.10.0"
pnpm = "8.12.0"

[settings]
auto-install = true
# Full-stack project
node = "20.10.0"
pnpm = "8.12.0"
python = "3.12.0"
rust = "1.75.0"

[settings]
auto-install = true
detect-strategy = "prefer-prototools"
# Rust project
rust = "1.75.0"

[settings]
auto-install = true

Shell Setup:

# Bash
echo 'eval "$(proto activate bash)"' >> ~/.bashrc

# Zsh
echo 'eval "$(proto activate zsh)"' >> ~/.zshrc

CI Integration:

# GitHub Actions
- uses: moonrepo/setup-toolchain@v0
  with:
    auto-install: true
Changes

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.

  1. 4d ago First seen · 112 lines · 0 tokens per session scan A 68242c528938

Subscribe to this mod's changes

proto-setup is an agent published in the GitHub repository hyperb1iss/moonrepo-skill (5 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 681 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.