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-end-to-endgit 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-end-to-end)<a href="https://agentmods.dev/skills/zhonghao1995/agentic-mike-plus/mike-end-to-end"><img src="https://agentmods.dev/badge/skills/zhonghao1995/agentic-mike-plus/mike-end-to-end/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zhonghao1995/agentic-mike-plus/mike-end-to-end"><img src="https://agentmods.dev/badge/skills/zhonghao1995/agentic-mike-plus/mike-end-to-end.svg" alt="Reviewed on agentmods" width="80" 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.00098 | $0.01636 |
| Opus 5 | $0.00049 | $0.00818 |
| Sonnet 5 | $0.00020 | $0.00327 |
| Haiku 4.5 | $0.00010 | $0.00164 |
Grade A, and why
mike-end-to-end 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 12d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MIKE+ End-to-End (SOP)
The other mike-* skills describe one tool group each. This one says how they fit
together, what must be true before a number or figure is reported, and when to stop.
1. Pick an operating mode (state it in the first reply)
| Mode | When | Chain | License |
|---|---|---|---|
| A. Read / plot only | a .res1d already exists, or no MIKE+ install |
mike-results -> mike-plot -> mike-audit |
none |
| B. Run an existing model | a .sqlite and a goal ("run the 1-year storm") |
copy -> mike-model -> (mike_set_scenario) -> mike-runner -> mike-results -> mike-plot -> mike-audit |
yes |
| C. What-if / compare | "what if the pipe were 0.5 m", "before vs after" | baseline copy + variant copy -> mike-params (variant only) -> mike-runner x2 -> mike-compare -> mike-audit |
yes |
| D. Import from SWMM | an EPA SWMM .inp (SWMMCanada, agentic-swmm) |
mike-import -> then B or C |
yes |
| E. New rainfall | a CSV storm / gauge record to drive the model | mike-rain -> point the model's rainfall boundary at the .dfs0 (mike-params) -> B |
rain: none, run: yes |
If the goal only needs Mode A, do not touch mikeplus at all: it is faster and needs no license.
2. Standard run directory (create it, use it everywhere)
runs/<case>/
00_model/ COPY of the whole model folder (.sqlite, .mupp, .dfs0, hotstart .res1d ...)
01_inputs/ rain CSV/.dfs0 you produced, notes
02_results/ the engine writes next to the model: 00_model/<name>_m1d - Result Files/*.res1d
03_plots/ every PNG
manifest.json mike_manifest_write, written last
For Mode C use 00_model_baseline/ and 00_model_<variant>/: two independent copies.
3. Hard rules
- Copy first, always the whole folder. mikeplus has no undo and the MIKE 1D engine writes result files (and a
.log) next to the model; external files (rain.dfs0, hotstart,.mupp) are referenced relatively, so copying only the.sqlitebreaks the run. - Gate on
status, notok.mike_runreturnsok:truewhenever the call returned. Usable =statusin{ok, completed_with_warnings};completed_with_errors/incomplete/unknown= do not use the results, surfaceerrors,warnings,log_file. - Discover ids before using them.
mike_model_info(setups, scenarios),mike_results_list(quantities, element ids),mike_get_values(current values). Never invent an element id, table or column. - Warm-up. Global peaks can sit at t≈0 (initial condition). Pass
skip_hourstomike_results_summary/mike_results_compare/mike_results_flooding/mike_plot_profileand always reportpeak_time. - Variants are copies, not scenarios.
mike_set_scenarioonly activates scenarios that already exist in the model (prepared in the GUI). Table edits made "inside" a scenario are not isolated (seemike-compare), so a what-if edit goes on a separate model copy. - License boundary. run / edit / scenario / import need MIKE+ + a checked-out license; results / plots / compare / rain / manifest do not. On a license failure ("license not available", demo mode, an edit that "did not persist", an import that "exceeds the demo limit") stop that branch and report it; do not retry in a loop, the seat is rate-limited and re-tries make it worse.
- Evidence only. Report a number only from a tool return; report a figure only when the tool returned
ok:trueandpng; say "not run" for anything skipped.
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.
- 12d ago First seen · 87 lines · 98 tokens per session scan A cabb37f9e7c2
mike-end-to-end is a skill published in the GitHub repository Zhonghao1995/Agentic-MIKE-Plus (7 stars, last pushed 27d ago), licensed MIT. It adds 98 tokens to every session and 1,636 once invoked, about $0.0005 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…