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 CodeInfinity1/Stram --skill rss-and-blog-monitoringgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/rss-and-blog-monitoring)<a href="https://agentmods.dev/skills/codeinfinity1/stram/rss-and-blog-monitoring"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/rss-and-blog-monitoring/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/codeinfinity1/stram/rss-and-blog-monitoring"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/rss-and-blog-monitoring.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.00036 | $0.00452 |
| Opus 5.5 | $0.00014 | $0.00181 |
| Sonnet 5.5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
rss-and-blog-monitoring 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 1mo 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
RSS And Blog Monitoring
Purpose
Track recurring web sources and produce useful summaries without building hidden polling behavior. Native triggers/automation should be explicit and bounded.
When To Use
Use for RSS feeds, blog updates, release notes, newsletters, changelogs, and scheduled briefings.
Inputs And Evidence
- Feed/blog URLs, cadence, summary format, filters, and notification preference.
- Current page/feed evidence and prior memory.
Tool Map
fetch_webpageresearch_webpagesrss_feed_readrss_watch_preparerss_watch_listactivity_ingestmemory_writecognitive_trigger_recordwrite_note
Workflow
- Identify sources and cadence.
- Use
rss_feed_readfor RSS or Atom feeds; usefetch_webpage/research_webpagesfor ordinary blog pages. - Summarize changes with source links and dates.
- Record durable watch intent with
rss_watch_prepareonly when the user wants ongoing monitoring. - Inspect existing prepared watches with
rss_watch_list. - Use trigger/automation tools for scheduled checks only after explicit approval.
- Report missing scheduler/credential gaps separately from feed parsing.
Native Implementation Boundaries
- Do not import external reference blogwatcher or external reference RSS plugins.
- Feed parsing and watch preparation must use Stram-owned tools.
- Prepared watch artifacts do not start polling.
- Do not silently run background polling.
Safety And Approval
- Respect source terms and rate limits.
- Avoid noisy notifications.
- Do not subscribe the user externally without approval.
Verification
- Source links and timestamps prove current summary.
- RSS watch paths prove prepared intent; trigger IDs prove scheduled monitoring.
- Missing adapter status should be explicit.
Failure Modes
- Summarizing stale pages.
- Creating hidden recurring work.
- Missing source attribution.
References
- Shortlist item:
rss-and-blog-monitoring.
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.
- 1mo ago First seen · 71 lines · 36 tokens per session scan A 1e2b6717983a
rss-and-blog-monitoring is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 452 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
ask-agents
Send a task or question to Claude Code and/or Gemini as external subagents and report back what they said. Use when the user asks to ask Claude, ask Gemini, ask both, get a second opinion, split reviewer roles, or compare external agents.
review-plan
Review a proposed plan with a single-pass structured critique and a clear verdict. Use when the user asks to review a plan, stress-test a plan, critique a workflow, identify risks, or improve an execution sequence.
alive:settings
The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…
lark-contact
A Feishu (Lark) contacts tool for finding users or bots and looking up their profiles and contact details.
oci-services-expert
Expert guidance on Oracle Cloud Infrastructure services, architecture patterns, cost optimization, and deployment strategies. Use when designing on OCI, selecting OCI services, estimating cost, or applying OCI enterprise best practices.
openai-agentkit
Build production multi-agent systems with OpenAI AgentKit and the Agents SDK — orchestration, handoffs, and routines. Use when writing agents against OpenAI's AgentKit/Agents SDK or porting an agent design to the OpenAI stack.