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-onboardnpx skills add bleedmode/dearuser --skill dearuser-onboardgit 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-onboard)<a href="https://agentmods.dev/skills/bleedmode/dearuser/dearuser-onboard"><img src="https://agentmods.dev/badge/skills/bleedmode/dearuser/dearuser-onboard.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 | $0.00023 | $0.00348 |
| Opus 5 | $0.00012 | $0.00174 |
| Sonnet 5 | $0.00005 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
dearuser:onboard 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
Dear User — Onboard
Run the guided onboarding flow using the Dear User MCP server.
What to do
- Try calling
mcp__dearuser__onboardwith no arguments to start. - If the tool is not available (first turn of session — MCP tools load lazily), use this Bash fallback:
For subsequent steps:npx -y -p @poisedhq/dearuser-mcp dearuser-run onboard 2>/dev/nullnpx -y -p @poisedhq/dearuser-mcp dearuser-run onboard '{"step":"<nextStep>","answer":"<user answer>","state":"<state>"}' 2>/dev/null - Output the returned text EXACTLY as your response — do NOT summarize, rephrase, or wrap it.
- Collect the user's answer.
- Call again with
step(from previous response's nextStep),answer(user's reply), andstate(from previous response, passed back verbatim). - Repeat until the response contains
done: true, then show the final plan.
Rules
- The
stateparameter is opaque. Pass it back unchanged — never parse or modify it. - Each step's output is pre-formatted. Show it exactly as returned, then wait for the user's answer.
- Do NOT ask your own questions — the tool provides the questions.
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 · 32 lines · 23 tokens per session scan A 123256cb279a
dearuser:onboard is a skill published in the GitHub repository bleedmode/dearuser (0 stars, last pushed 27d ago), licensed MIT. It adds 23 tokens to every session and 348 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 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.
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
assets-prefab-save
Save the currently opened prefab edit stage back to its prefab asset without exiting the stage. Pair with 'assets-prefab-open' to enter the edit mode first.
console-get-logs
Retrieve Unity Editor logs from the MCP plugin's LogCollector, optionally filtered by log type or time window. Useful for debugging and monitoring Editor activity.
assets-shader-list-all
List all shaders available in the project assets and packages, sorted by name. Use this to discover a valid shaderName for 'assets-material-create'.
profiler-load-data
Read back a previously-saved JSON snapshot from profiler-save-data and return its raw text.