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-historynpx skills add bleedmode/dearuser --skill dearuser-historygit 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-history)<a href="https://agentmods.dev/skills/bleedmode/dearuser/dearuser-history"><img src="https://agentmods.dev/badge/skills/bleedmode/dearuser/dearuser-history.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.00042 | $0.00594 |
| Opus 5 | $0.00021 | $0.00297 |
| Sonnet 5 | $0.00008 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
dearuser:history 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 4d 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 — History
Hent eksisterende rapporter uden at køre en ny scan. Brug dette når brugeren vil se seneste score, trend over tid, eller hvad der ændrede sig — ikke når de vil have friske data (kør collab/health/security direkte i stedet).
Hvornår bruges hvad
- "Vis seneste rapport" / "hvad sagde nattens scan?" / "show me the latest" →
format: "summary" - "Er scoren blevet bedre?" / "vis trend" / "hvordan går det over tid" →
format: "trend" - "Hvad ændrede sig?" / "hvad er nyt?" / "hvad gik galt?" →
format: "regression" - Specifik historisk rapport (bruger har et run-ID) →
run_id: "<id>"
Scope kan snævre ind: "collab", "health", "security", eller "all" (default).
Trin 1: Kør tool
- Prøv
mcp__dearuser__historymed relevante parametre. - Hvis tool'et ikke er tilgængeligt (første turn i session — MCP tools loader lazy), brug Bash-fallback:
Med parametre (JSON):npx -y -p @poisedhq/dearuser-mcp dearuser-run history 2>/dev/nullnpx -y -p @poisedhq/dearuser-mcp dearuser-run history '{"format":"trend","scope":"security"}' 2>/dev/null - Output HELE rapporten som dit svar — summér ikke, forkort ikke.
Trin 2: Fresh-scan CTA
Efter summary/trend: hvis data er >24t gammelt, tilbyd at køre en frisk scan (collab/health/security). Rapporter tager ~30 sek.
Efter regression: hvis der er nye findings, tilbyd at køre implement_recommendation på pending recs, eller en frisk scan for at verificere fix.
Regler
- Rapport-delen: verbatim, ingen commentary.
- Dansk svar hvis brugeren skriver på dansk.
- Brug ikke dette tool til at "spare tid" på en scan brugeren eksplicit bad om — hvis de sagde "kør security", kør security. History er til eksisterende rapporter.
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.
- 4d ago First seen · 44 lines · 42 tokens per session scan A fb0eb2bf8e53
dearuser:history is a skill published in the GitHub repository bleedmode/dearuser (0 stars, last pushed 28d ago), licensed MIT. It adds 42 tokens to every session and 594 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…
emissary
Compose, send, or run an Egregore emissary — portable handoff v1 artifacts with server-rendered HTML at egregore.xyz. Use for /emissary, "make/send/run an emissary", or when a user pastes an egregore.xyz/emissary/e/ link.
announce
Send an announcement to the Telegram group with a draft-then-approve flow. Use for /announce, telling the team something, or notifying everyone at once — not messaging one person or a structured handoff.
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…