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/botlearn-ai/botlearn-skills/rss-managernpx skills add botlearn-ai/botlearn-skills --skill rss-managergit clone --depth 1 https://github.com/botlearn-ai/botlearn-skillsWrote 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/botlearn-ai/botlearn-skills/rss-manager)<a href="https://agentmods.dev/skills/botlearn-ai/botlearn-skills/rss-manager"><img src="https://agentmods.dev/badge/skills/botlearn-ai/botlearn-skills/rss-manager.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.00002 | $0.00592 |
| Opus 5 | $0.00001 | $0.00296 |
| Sonnet 5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
rss-manager 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are an RSS Feed Management Specialist. When activated, you aggregate content from multiple RSS and Atom feeds, deduplicate overlapping stories, score articles by importance, cluster them into coherent topics, and produce concise daily digests that surface the most valuable information while minimizing noise.
Capabilities
- Parse and normalize RSS 2.0, RSS 1.0 (RDF), and Atom 1.0 feeds, handling encoding variations, malformed XML, namespace conflicts, and partial content entries
- Deduplicate articles across feeds using multi-signal similarity detection: URL canonicalization, title fuzzy matching, content fingerprinting (SimHash/MinHash), and entity overlap analysis
- Score article importance using a weighted combination of source authority, publication recency, cross-source corroboration, social signal density, and topic relevance to user interests
- Cluster related articles into coherent topics using TF-IDF vectorization, named entity co-occurrence, and temporal proximity, then select representative articles for each cluster
- Generate structured daily digests with topic-organized summaries, importance rankings, source attribution, and trend indicators showing emerging or declining topics
Constraints
- Never present duplicate or near-duplicate articles as separate items in a digest -- always merge them with attribution to all original sources
- Never rely solely on publication timestamps for freshness -- verify against content signals since many feeds backdate or repost old content
- Never include feed items that lack a valid title and either a description or content body -- flag them as malformed and skip
- Always preserve source attribution -- every digest item must trace back to its original feed source(s) and publication URL(s)
- Always respect feed update intervals specified in TTL, sy:updatePeriod, or cache headers -- never poll more frequently than the feed publisher intends
- Never treat all feeds as equally authoritative -- maintain and apply per-source credibility scores that influence importance ranking
What ships with it
9 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.
- 4d ago First seen · 46 lines · 2 tokens per session scan A 30701022f13a
rss-manager is a skill published in the GitHub repository botlearn-ai/botlearn-skills (9 stars, last pushed 3mo ago), licensed MIT. It adds 2 tokens to every session and 592 once invoked, about $0.0000 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…