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/danielbodnar/skills/init-misegit clone --depth 1 https://github.com/danielbodnar/skillsWhat 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 | $0.00013 | $0.00478 |
| Opus 5 | $0.00006 | $0.00239 |
| Sonnet 5 | $0.00003 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
init-mise 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 3d 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
Set up mise in the current project by creating a .mise.toml configuration file.
Steps
Detect project type
Examine existing files to determine the project type:
package.jsonwithbun.lockorbun.lockb-> Bun projectwrangler.jsoncorwrangler.toml-> Cloudflare Workers projectCargo.toml-> Rust projectCargo.tomlandpackage.json-> Rust + Bun project- No indicators -> ask the user
Check for existing configuration
Look for existing tool version files:
.mise.toml-- already configured, offer to update.tool-versions-- offer to migrate to.mise.toml.nvmrcor.node-version-- extract Node version, offer to migraterust-toolchain.toml-- extract Rust channel, offer to migrate
If any exist, show the user what was found and ask whether to migrate or replace.
Generate .mise.toml
Create a .mise.toml file using the appropriate template from the mise-config skill based on the detected project type. Use the following defaults:
- Bun:
bun = "latest",just = "latest" - Cloudflare Workers:
bun = "latest",node = "22",just = "latest" - Rust:
rust = "stable",just = "latest" - Rust + Bun:
bun = "latest",rust = "stable",just = "latest"
Activate and install
After creating the file, run:
mise trustto mark the directory as trustedmise installto install all specified tools
Clean up migrated files
If migrating from another tool version manager, ask the user whether to delete the old files (.nvmrc, .node-version, .tool-versions, rust-toolchain.toml).
Summary
Report what was configured:
- List the tools and versions in
.mise.toml - Confirm tools were installed successfully
- Note any migration actions taken
- Suggest adding
.mise.tomlto version control
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.
- 3d ago First seen · 59 lines · 13 tokens per session scan A ff706b772cf1
init-mise is a command published in the GitHub repository danielbodnar/skills (2 stars, last pushed 25d ago), licensed MIT. It adds 13 tokens to every session and 478 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.