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/aksika/abtars/rssnpx skills add aksika/abtars --skill rssgit clone --depth 1 https://github.com/aksika/abtarsWhat 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.00018 | $0.00360 |
| Opus 5 | $0.00009 | $0.00180 |
| Sonnet 5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
rss 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 3d 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 Feed Fetcher
Usage
abtars-rss --feeds <path-to-feeds.json> [--hours N]
--feeds(required): path to a JSON file containing feed configs--hours(optional, default 24): only include items from the last N hours
Feeds file format
[
{ "url": "https://example.com/rss", "name": "Example Feed" },
{ "url": "https://other.com/atom.xml", "name": "Other Feed", "keywords": ["AI", "finance"] }
]
url: RSS/Atom feed URL (or SEC EDGAR JSON endpoint)name: display name for the sourcekeywords(optional): only keep items matching these keywords
Output
Writes to ~/.abtars/workspace/rss/<feedname>/<date>.json and prints JSON to stdout.
Task integration
Place your feeds file alongside your task with the _feeds.json suffix:
tasks/
daily-ai-report.md
daily-ai-report_feeds.json ← auto-injected into task context
In your task .md, instruct: "Run abtars-rss --feeds tasks/daily-ai-report_feeds.json"
Do not
- Do not hardcode feed URLs in task instructions — put them in the
_feeds.jsonfile - Do not parse HTML pages with this tool — it only handles RSS/Atom XML and SEC EDGAR JSON
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.
- 3d ago First seen · 52 lines · 18 tokens per session scan A 3489f25f3af4
rss is a skill published in the GitHub repository aksika/abtars (9 stars, last pushed 3d ago), licensed Apache-2.0. It adds 18 tokens to every session and 360 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
agent-quorum-manager
Agent skill for quorum-manager - invoke with $agent-quorum-manager.
agent-agent
Agent skill for agent - invoke with $agent-agent.
agent-crdt-synchronizer
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer.
agent-adaptive-coordinator
Agent skill for adaptive-coordinator - invoke with $agent-adaptive-coordinator.
agent-performance-monitor
Agent skill for performance-monitor - invoke with $agent-performance-monitor.
agent-code-review-swarm
Agent skill for code-review-swarm - invoke with $agent-code-review-swarm.