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 beel-collab/presets.dev --skill mise-configuratorgit clone --depth 1 https://github.com/beel-collab/presets.devWrote 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/beel-collab/presets.dev/mise-configurator)<a href="https://agentmods.dev/skills/beel-collab/presets.dev/mise-configurator"><img src="https://agentmods.dev/badge/skills/beel-collab/presets.dev/mise-configurator.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.00021 | $0.00887 |
| Opus 5 | $0.00010 | $0.00443 |
| Sonnet 5 | $0.00004 | $0.00177 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
mise-configurator 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mise Configurator
Overview
This skill generates clean, production-ready mise.toml configurations for local development environments and CI/CD pipelines.
It helps standardize runtime versions, simplify onboarding, replace legacy version managers like asdf, nvm, and pyenv, and create reproducible multi-language environments with minimal setup effort.
When to Use This Skill
- Use when you need to create or update a
mise.toml - Use when working with Node.js, Python, Go, Rust, Java, Bun, Terraform, or mixed stacks
- Use when the user asks about CI/CD runtime setup using mise
- Use when migrating from
.tool-versions,asdf,nvm, orpyenv - Use when standardizing tool versions across teams or monorepos
How It Works
Step 1: Detect Project Context
Inspect available repository files such as:
package.jsonpnpm-lock.yamlpyproject.tomlrequirements.txtgo.modCargo.toml.tool-versionsDockerfile- GitHub Actions or CI files
Infer languages, package managers, and pinned versions.
Step 2: Generate mise.toml
Create a minimal, valid, copy-paste-ready configuration using:
- existing pinned versions when found
- explicit user-provided target versions when absent
- practical defaults for developer productivity
- concrete pinned versions in shared production configs
Step 3: Add Bootstrap Commands
Provide setup commands such as:
mise trust
mise install
Step 4: Generate CI/CD Integration
If requested, generate pipeline examples using mise with caching and runtime installation.
Examples
Example 1: Node.js + pnpm Project
[tools]
node = "22.11.0"
pnpm = "9.15.0"
Example 2: Python + GitHub Actions
[tools]
python = "3.12.7"
poetry = "1.8.4"
steps:
- uses: actions/checkout@v4
- uses: jdx/mise-action@v2
- run: poetry install
- run: pytest
Best Practices
-
✅ Respect versions already pinned in the repository
-
✅ Keep configs minimal and readable
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.
- 4d ago First seen · 152 lines · 21 tokens per session scan A a2b64dee3a1c
mise-configurator is a skill published in the GitHub repository beel-collab/presets.dev (2 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 887 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-09-03.
Other skills, from other repositories
github-triage
Triage GitHub issues through a label-based state machine with interactive grilling sessions. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
backlog
Capture single backlog items, or list and triage an existing project backlog. Use this skill whenever the user wants to file a bug, feature request, or backlog item without writing a full PRD, including casual requests mid-conversation like "create an issue for that", "add this to the backlog", or "file a quick bug…
reframe-voice
Write, rewrite, or review content in the evidence-led reframe voice style. Use when the user explicitly asks to write in "reframe voice" or "reframe style". Do NOT use for general writing tasks.
to-tickets
Break a plan, spec, or the current conversation into independently-grabbable tickets on the project issue tracker using tracer-bullet vertical slices, each declaring the tickets that block it. Use when user wants to convert a plan or spec into tickets, create implementation tickets, or break down work into issues.
to-spec
Turn the current conversation context into a spec and submit it as a GitHub issue. Use when user wants to create a spec or PRD from the current context.
nx-workspace
Configure, explore, and optimize Nx monorepo workspaces. Use when setting up Nx, exploring workspace structure, configuring project boundaries, analyzing affected projects, optimizing build caching, or implementing CI/CD with affected commands. Keywords — nx, monorepo, workspace, projects, targets, affected. Do NOT…