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 Zhonghao1995/Agentic-MIKE-Plus --skill mike-paramsgit clone --depth 1 https://github.com/Zhonghao1995/Agentic-MIKE-PlusWrote 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/zhonghao1995/agentic-mike-plus/mike-params)<a href="https://agentmods.dev/skills/zhonghao1995/agentic-mike-plus/mike-params"><img src="https://agentmods.dev/badge/skills/zhonghao1995/agentic-mike-plus/mike-params.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.00086 | $0.00668 |
| Opus 5 | $0.00043 | $0.00334 |
| Sonnet 5 | $0.00017 | $0.00134 |
| Haiku 4.5 | $0.00009 | $0.00067 |
Grade A, and why
mike-params 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.
How it starts
The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MIKE+ Parameters
Reads and edits values in the MIKE+ model database tables (via mikeplus). This is the "edit the model" capability that sits between mike-model (overview) and mike-runner (execute).
Tools
mike_get_values—{sqlite, table, columns?, muids?}→ current values. Read-only. Use to identify a parameter before changing it.mike_set_values—{sqlite, table, values, muids | all}→ applies the change and returns before/after for the affected rows. Mutates the database.
Common tables / columns
msm_Link— pipes/reaches:Diameter,Width,Height,Manning(Manning's M; higher = smoother),MaterialID,TypeNo.msm_Node— manholes/nodes:GroundLevel,InvertLevel,Diameter.msm_Catchment— catchments: area / imperviousness / runoff parameters.msm_Project— simulation setups (used bymike_run'ssimulation).
Conventions (safety)
- Always operate on a COPY —
mike_set_valueswrites to the database and mikeplus has no undo. - Scope every edit. Pass
muidsto target specific elements; only setall=truewhen you truly mean every row. - Confirm with the returned
before/after(or a follow-upmike_get_values) before re-running. - Edit with the Base scenario active (or a scenario that shares Base's alternatives). Under a scenario with its own alternatives mikeplus cannot write and the tool errors "did not persist"; a variant for comparison is a second model COPY, not a scenario (see
mike-compare). - Boundary/rain changes: the rainfall boundary is
msm_BBoundary(TypeNo = 1;TSConnection= dfs0 path relative to the model folder,TimeseriesName= dfs0 item) — seemike-rain. - After editing, re-run with
mike_runand quantify the effect withmike_results_compare(mike-compare).
Orchestration (identify -> change -> re-run -> compare)
mike_model_info / mike_get_values -> identify current parameter
mike_set_values -> change it (on the variant copy) -> before/after
mike_run -> new .res1d
mike_results_compare / mike_plot_compare -> against the baseline run
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 · 36 lines · 86 tokens per session scan A 8659a279a123
mike-params is a skill published in the GitHub repository Zhonghao1995/Agentic-MIKE-Plus (7 stars, last pushed 21d ago), licensed MIT. It adds 86 tokens to every session and 668 once invoked, about $0.0004 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 skills, from other repositories
autonomous-researcher
End-to-end research pipeline: scoping, literature review, hypothesis formation, synthesis, empirical validation, and written output.
research-librarian
Organize sources, claims, and open questions so research stays traceable.
Jupyter Live Kernel
Guides notebook-first analysis with reproducible kernels, inspectable data loading, and explicit promotion paths back into durable code.
arXiv
Search, filter, and summarize arXiv papers with explicit titles, authors, dates, and paper links before drawing conclusions.
ras-end-to-end
Standard operating procedure for an auditable, headless HEC-RAS workflow via the hec-ras MCP server — how to plan, copy, edit boundaries, run, QA-gate, read results, compare, plot, audit, and safely stop. Use FIRST whenever an agent is handed a HEC-RAS project (.prj folder) or a results file (.p##.hdf) plus a…
ras-model
Inspect and edit a HEC-RAS project without the GUI via the hec-ras MCP server — list plans / geometries / flow files / boundary conditions (rasprojectinfo), copy the whole project safely (rasprojectcopy), change plan settings such as simulation window, time step, output interval, cores, geometry or flow file…