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 skills/bleedmode/dearuser/dearuser-healthnpx skills add bleedmode/dearuser --skill dearuser-healthgit clone --depth 1 https://github.com/bleedmode/dearuserWrote 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/bleedmode/dearuser/dearuser-health)<a href="https://agentmods.dev/skills/bleedmode/dearuser/dearuser-health"><img src="https://agentmods.dev/badge/skills/bleedmode/dearuser/dearuser-health.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.00048 | $0.00412 |
| Opus 5 | $0.00024 | $0.00206 |
| Sonnet 5 | $0.00010 | $0.00082 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
dearuser:health 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 5d 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
Dear User — Health
Kør et strukturelt sundhedstjek med Dear User MCP serveren. Giver en 0-100 score plus kategori-breakdown og fund rangeret efter alvorlighed.
Kør rapport
- Prøv at kalde
mcp__dearuser__healthmed default parametre (ingen argumenter — global scope, alle fund). - Hvis tool'et ikke er tilgængeligt (første turn i session — MCP tools loader lazy), brug Bash-fallback:
npx -y -p @poisedhq/dearuser-mcp dearuser-run health 2>/dev/null - Output HELE rapporten som dit svar — summér ikke, forkort ikke, tilføj ikke kommentarer i rapport-delen.
Hvis brugeren spørger om en specifik finding-type, send focus med relevant værdi (orphan, overlap, closure, substrate, mcp_refs, backup, stale_schedule). Bash: npx -y -p @poisedhq/dearuser-mcp dearuser-run health '{"focus":"orphan"}' 2>/dev/null
Efter rapporten
Hvis rapporten indeholder pending recommendations, tilbyd at implementere dem via mcp__dearuser__implement_recommendation. Spørg brugeren hvilke de vil køre.
Regler
- Rapporten er pre-formateret markdown. Vis den eksakt som returneret.
- Dansk svar hvis brugeren skriver på dansk.
- Hvis critical findings er relateret til leaked secrets, fremhæv at brugeren skal rotere dem straks.
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.
- 5d ago First seen · 31 lines · 48 tokens per session scan A e2ed045300ac
dearuser:health is a skill published in the GitHub repository bleedmode/dearuser (0 stars, last pushed 29d ago), licensed MIT. It adds 48 tokens to every session and 412 once invoked, about $0.0002 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
control-flow
Analyze and design control flows and data structures. Produces compact ASCII tree diagrams showing triggers, call chains, payload shapes, state mutations, and re-render effects. Use when user asks to diagram, trace, visualize, or design a flow or data structure.
tool-foundation-sprint-founding-hypothesis
Day 2 end capstone move of a Foundation Sprint. Compresses the sprint's full strategic frame into a single canonical sentence (the Founding Hypothesis) plus an assumption scorecard, why-we-believe, what-could-prove-us-wrong, and recommended next validation step. Use after Magic Lenses is signed. Strict canonical…
capture-usage4claude-screenshots
Automate Usage4Claude interface screenshots with CleanShot X on macOS. Use when Codex needs to capture localized Usage4Claude menu-bar popover screenshots, switch Usage4Claude display/language settings, save files such as [email protected], or troubleshoot CleanShot/window-capture automation that depends on…
tool-design-sprint-prototype-plan
Day 4 (Thursday) move of a Design Sprint that produces the planning artifact for the day. Output covers the prototype role plan (Maker, Stitcher, Writer, Asset Collector, Interviewer), prototype brief (what to build, fidelity bar, time allocation per role), canonical Five-Act Interview script (Welcome, Context, Intro…
preview-design
Render a real artifact through this branch's local MERIDIAN design code (not the published npm package) so the team can test the new Design Convention on the document / handoff / platform surfaces before it ships. Use for /preview-design, "preview the design convention", "render this with the new design", or Design…
utility-mermaid-diagrams
Teaches PMs to create syntactically valid mermaid diagrams by selecting the right diagram type for their communication need, following syntax validity rules, and validating before shipping. Covers all 15 mermaid diagram types with PM-relevant examples and a dual-lens navigation system.