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 voxpelli/vp-claude --skill raindrop-triagegit clone --depth 1 https://github.com/voxpelli/vp-claudeWrote 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/voxpelli/vp-claude/raindrop-triage)<a href="https://agentmods.dev/skills/voxpelli/vp-claude/raindrop-triage"><img src="https://agentmods.dev/badge/skills/voxpelli/vp-claude/raindrop-triage/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/voxpelli/vp-claude/raindrop-triage"><img src="https://agentmods.dev/badge/skills/voxpelli/vp-claude/raindrop-triage.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.00181 | $0.03287 |
| Opus 5 | $0.00090 | $0.01643 |
| Sonnet 5 | $0.00036 | $0.00657 |
| Haiku 4.5 | $0.00018 | $0.00329 |
Grade A, and why
raindrop-triage 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Raindrop Triage
Interactive triage of unsorted Raindrop bookmarks: deduplicate, detect research
bursts, cluster by theme, propose vocabulary-grounded tags, and move approved
bookmarks to AI-triaged. A second invocation with --promote classifies
AI-triaged items into AI-sorted (default), AI-gems (golden), AI-archive,
or AI-attention.
Arguments
--promote— run the promotion pass on AI-triaged bookmarks instead of the default unsorted triage--source <collection>— (promote only) override the default AI-triaged source. Use--source unsortedfor pre-triaged bookmarks.--limit N— override the default 200-bookmark fetch limit
Edge Cases
- Empty unsorted / empty AI-triaged — report "No bookmarks to triage" and exit cleanly.
- Raindrop MCP unavailable — report "Raindrop MCP unavailable — cannot triage" and exit. Do not attempt fallback.
- Vocabulary file missing — warn "Tag vocabulary not loaded — run
/tag-syncfirst for consistent tagging." Continue with copy-from-similar only, but note degraded tag quality in the session summary. - >200 bookmarks — triage the first page. Report remaining count and suggest re-running for the next batch.
- Partial
update_bookmarksfailure — report which bookmarks failed. Do not retry automatically — the user can re-run the skill. - BM unavailable — skip the cross-reference step (Step 9). Note "Basic Memory unavailable — skipping knowledge gap cross-reference" in the summary.
- Collection name collision — if a non-AI collection named "AI-triaged" (etc.) already exists, report the conflict and stop. Do not create a duplicate.
- Note field too long for attention append — if the bookmark note exceeds 10,000 characters after appending, warn the user and skip the append for that bookmark.
AI-Managed Collection Namespace
This skill operates within the AI-managed collection namespace:
| Collection | Purpose | Created by |
|---|---|---|
| AI-bookmarked | Session bookmark captures | /session-bookmarks |
| AI-triaged | Default landing zone for triaged unsorted bookmarks | This skill (lazy) |
| AI-sorted | Useful, organized bookmarks (the default promotion destination) | This skill (lazy) |
| AI-gems | Golden stuff — seminal papers, canonical references, high-reuse gems | This skill (lazy) |
| AI-archive | Low-reuse bookmarks (ephemeral shopping, dead pages, one-off lookups) | This skill (lazy) |
| AI-attention | Bookmarks needing human decision or further research | This skill (lazy) |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 370 lines · 181 tokens per session scan A d4d14e253820
raindrop-triage is a skill published in the GitHub repository voxpelli/vp-claude (3 stars, last pushed 12d ago), licensed MIT. It adds 181 tokens to every session and 3,287 once invoked, about $0.0009 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
synergy-tracker
Manage cross-project synergy tracking between sibling projects. Use when the user wants to log a shared pattern, a divergence, an extraction candidate, or something a sibling project has that this one doesn't. Also use when the user wants to promote synergy entries to Basic Memory (workflow 5). NOT for upstream…
upstream-tracker
Manage upstream issue tracking for this project. Use when the user wants to log a bug or friction point in a vendor package or npm dependency, review open upstream items, resolve a tracked issue, run a trend review, generate the upstream observations section of a sprint retrospective, promote upstream observations to…
retrospective
Run a sprint retrospective for this project. Use when the user says 'retrospective', 'retro', 'close out the sprint', 'what went well', 'generate retro', or wants to generate a RETRO-NN.md file. Reads UPSTREAM-.md files, recent git history, and conversation context to pre-populate the retrospective. Do NOT use for…
swarm-wave
Orchestrate multi-agent development sprints with wave-based parallelism. Use when the user wants to plan a swarm sprint, partition work into file-disjoint waves, map file contention across open issues, run a post-wave quality gate with review agents, manage agent backpressure, run a parallel research wave, or…
backlog-groomer
Manage the beads backlog for this project. Use when the user wants to review or triage open issues, reprioritize the backlog, identify obsolete issues to close, investigate a topic to inform future work, create new issues from research findings, or enrich an existing issue with external context. Trigger phrases…
harden-memories
Audit the bd remember store and recommend which entries to prune, so each one earns its per-session bd prime injection cost. Read-only: it proposes a triage table plus the exact bd forget / migration commands; you run them. Use when bd remember entries have accumulated, feel stale, redundant, or conflicting, or when…