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 hannesill/m4 --skill mimic-urine-output-rategit clone --depth 1 https://github.com/hannesill/m4Wrote 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/hannesill/m4/mimic-urine-output-rate)<a href="https://agentmods.dev/skills/hannesill/m4/mimic-urine-output-rate"><img src="https://agentmods.dev/badge/skills/hannesill/m4/mimic-urine-output-rate/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/hannesill/m4/mimic-urine-output-rate"><img src="https://agentmods.dev/badge/skills/hannesill/m4/mimic-urine-output-rate.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.00000 | $0.01239 |
| Opus 5 | $0.00000 | $0.00620 |
| Sonnet 5 | $0.00000 | $0.00248 |
| Haiku 4.5 | $0.00000 | $0.00124 |
Grade A, and why
mimic-urine-output-rate 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.
This is a copy
100% identical to mimic-apsiii-24h-raw — 985 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Reference SQL (matched-content control)
The following block is the public reference SQL used to construct the ground truth for this task. It is provided verbatim, without procedural prose, to test whether matched task-relevant content alone explains the WITH-SKILL gain.
-- ------------------------------------------------------------------
-- Title: Urine Output Rate
-- Calculates rolling urine output rates (mL/kg/hr) over 6, 12, and
-- 24-hour windows, normalized by patient weight. Used for KDIGO AKI
-- staging and SOFA renal component.
-- ------------------------------------------------------------------
-- Reference:
-- KDIGO Clinical Practice Guideline for Acute Kidney Injury.
-- Kidney Int Suppl. 2012;2(1):1-138.
-- Adapted from mimic-code urine_output_rate.sql
-- Uses self-join for rolling window aggregation.
WITH tm AS (
SELECT
ie.stay_id,
MIN(charttime) AS intime_hr,
MAX(charttime) AS outtime_hr
FROM mimiciv_icu.icustays AS ie
INNER JOIN mimiciv_icu.chartevents AS ce
ON ie.stay_id = ce.stay_id
AND ce.itemid = 220045
AND ce.charttime > ie.intime - INTERVAL '1' MONTH
AND ce.charttime < ie.outtime + INTERVAL '1' MONTH
GROUP BY
ie.stay_id
), uo_tm AS (
SELECT
tm.stay_id,
CASE
WHEN LAG(charttime) OVER w IS NULL
THEN DATE_DIFF('microseconds', intime_hr, charttime)/60000000.0
ELSE DATE_DIFF('microseconds', LAG(charttime) OVER w, charttime)/60000000.0
END AS tm_since_last_uo,
uo.charttime,
uo.urineoutput
FROM tm
INNER JOIN mimiciv_derived.urine_output AS uo
ON tm.stay_id = uo.stay_id
WINDOW w AS (PARTITION BY tm.stay_id ORDER BY charttime NULLS FIRST)
), ur_stg AS (
SELECT
io.stay_id,
io.charttime,
SUM(DISTINCT io.urineoutput) AS uo,
SUM(
CASE
WHEN DATE_DIFF('microseconds', iosum.charttime, io.charttime)/3600000000.0 <= 5
THEN iosum.urineoutput
ELSE NULL
END
) AS urineoutput_6hr,
SUM(
CASE
WHEN DATE_DIFF('microseconds', iosum.charttime, io.charttime)/3600000000.0 <= 5
THEN iosum.tm_since_last_uo
ELSE NULL
END
) / 60.0 AS uo_tm_6hr,
SUM(
CASE
WHEN DATE_DIFF('microseconds', iosum.charttime, io.charttime)/3600000000.0 <= 11
THEN iosum.urineoutput
ELSE NULL
END
) AS urineoutput_12hr,
SUM(
CASE
WHEN DATE_DIFF('microseconds', iosum.charttime, io.charttime)/3600000000.0 <= 11
THEN iosum.tm_since_last_uo
ELSE NULL
END
) / 60.0 AS uo_tm_12hr,
SUM(iosum.urineoutput) AS urineoutput_24hr,
SUM(iosum.tm_since_last_uo) / 60.0 AS uo_tm_24hr
FROM uo_tm AS io
LEFT JOIN uo_tm AS iosum
ON io.stay_id = iosum.stay_id
AND io.charttime >= iosum.charttime
AND io.charttime <= (
iosum.charttime + INTERVAL '23' HOUR
)
GROUP BY
io.stay_id,
io.charttime
)
SELECT
ur.stay_id,
ur.charttime,
wd.weight,
ur.uo,
ur.urineoutput_6hr,
ur.urineoutput_12hr,
ur.urineoutput_24hr,
CASE
WHEN uo_tm_6hr >= 6
THEN ROUND(TRY_CAST((
ur.urineoutput_6hr / wd.weight / uo_tm_6hr
) AS DECIMAL), 4)
END AS uo_mlkghr_6hr,
CASE
WHEN uo_tm_12hr >= 12
THEN ROUND(TRY_CAST((
ur.urineoutput_12hr / wd.weight / uo_tm_12hr
) AS DECIMAL), 4)
END AS uo_mlkghr_12hr,
CASE
WHEN uo_tm_24hr >= 24
THEN ROUND(TRY_CAST((
ur.urineoutput_24hr / wd.weight / uo_tm_24hr
) AS DECIMAL), 4)
END AS uo_mlkghr_24hr,
ROUND(TRY_CAST(uo_tm_6hr AS DECIMAL), 2) AS uo_tm_6hr,
ROUND(TRY_CAST(uo_tm_12hr AS DECIMAL), 2) AS uo_tm_12hr,
ROUND(TRY_CAST(uo_tm_24hr AS DECIMAL), 2) AS uo_tm_24hr
FROM ur_stg AS ur
LEFT JOIN mimiciv_derived.weight_durations AS wd
ON ur.stay_id = wd.stay_id
AND ur.charttime > wd.starttime
AND ur.charttime <= wd.endtime
AND wd.weight > 0
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 · 132 lines · 0 tokens per session scan A 407d4dd0dfb1
mimic-urine-output-rate is a skill published in the GitHub repository hannesill/m4 (43 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,239 tokens. A static security scan graded it A with 0 findings. It is 100% identical to mimic-apsiii-24h-raw, differing in 985 lines, and is treated as a copy.
Other skills, from other repositories
arbor-agent-orchestrator
Top-level controller for recreating the open-source AutoResearch workflow as a suite of skills. Use when the user asks to run, emulate, extract, validate, or refine Arbor/AutoResearch behavior, especially when a coordinator must load phase skills for setup, ideation, executors, merge evaluation, novelty search…
embeddings
Vector embeddings with HNSW indexing, sql.js persistence, and hyperbolic support. 75x faster with agentic-flow integration. Use when: semantic search, pattern matching, similarity queries, knowledge retrieval. Skip when: exact text matching, simple lookups, no semantic understanding needed.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
migration-review
Review database migration files when a change adds or modifies paths under migrations/. Use it before merge to collect forward, rollback, locking, and data-safety evidence.
azure-resource-manager-postgresql-dotnet
Azure PostgreSQL Flexible Server SDK for .NET. Database management for PostgreSQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "PostgreSQL", "PostgreSqlFlexibleServer", "PostgreSQL Flexible Server", "Azure Database for…