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-feedbacknpx skills add bleedmode/dearuser --skill dearuser-feedbackgit clone --depth 1 https://github.com/bleedmode/dearuserWhat 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.00028 | $0.00515 |
| Opus 5 | $0.00014 | $0.00258 |
| Sonnet 5 | $0.00006 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
dearuser:feedback 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 yesterday.
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 — Feedback
Send the user's message to the Dear User founder inbox.
What to do
- Take whatever the user said (or the argument text) and pass it verbatim as
message. Do NOT rewrite, shorten, or summarise. - Try calling
mcp__dearuser__feedbackwith{ "message": "<the user's text>" }. - If the tool is not available (first turn of session — MCP tools load lazily), use this Bash fallback. Pipe the message via stdin so apostrophes, quotes, and newlines in the user's text don't break shell quoting:
jq -Rn --arg msg "$(cat <<'END_OF_DU_MSG'
<the user's text — verbatim, any content, no escaping> END_OF_DU_MSG )" '{message:$msg}' | npx -y -p @poisedhq/dearuser-mcp dearuser-run feedback -
The `<<'END_OF_DU_MSG'` (quoted heredoc marker) prevents bash from interpreting any character in the message — apostrophes, `$`, backticks, backslashes all pass through literally. `jq` then produces safe JSON and pipes it to `dearuser-run -` which reads from stdin.
If the command prints to stderr or exits non-zero, show that output to the user — the message was NOT sent.
4. Show the returned confirmation to the user exactly as returned — it's already short and friendly.
## Optional parameters
Only include these when the user explicitly provided them:
- `rating` (1–5) — only when the user typed a number
- `context` — `collab` / `security` / `health` / `wrapped` / `general`. Default to the tool they just ran, or `general`.
- `opt_in_followup` + `email` — only when the user explicitly asked for a reply
## Rules
- Write-only. This is the one place Dear User sends data out. Never invoke it without an explicit user message.
- Never infer sentiment to fill in `rating`. Leave it out unless the user said a number.
- If the tool returns an error, show the error text — the message was NOT sent.
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.
- yesterday First seen · 38 lines · 28 tokens per session scan A 2103455309c1
dearuser:feedback is a skill published in the GitHub repository bleedmode/dearuser (0 stars, last pushed 26d ago), licensed MIT. It adds 28 tokens to every session and 515 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.
triage-reviews
Fetch PR review comments, verify each against real code/docs, fix valid issues, commit and push.
liveagent-code-review
Review an open GitHub pull request or the current local branch and working tree with parallel, independent reviewers and evidence-based validation. Use when the user asks for code review, invokes the Code Review action from Git Review, or explicitly mentions this skill.
deploy
Trigger the claude-desktop-extra Build & Release GitHub Actions pipeline (build-and-release.yml). With no argument the skill inspects the changes since the last release and decides forcerebuild itself; "/deploy force" / "/deploy no-force" override.
dashboard
See your recent sessions, open handoffs, and current work at a glance. Use for /dashboard, checking your personal status — not the team-wide view (/activity).
view
Generate a branded HTML artifact from Egregore data (quest, handoff, activity, board, network, or any document) and open it in the browser. Use for /view, 'render this', or 'show me visually'.