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/yusufkaraaslan/skill_seekers/rssnpx skills add yusufkaraaslan/Skill_Seekers --skill rssgit clone --depth 1 https://github.com/yusufkaraaslan/Skill_SeekersWrote 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/yusufkaraaslan/skill_seekers/rss)<a href="https://agentmods.dev/skills/yusufkaraaslan/skill_seekers/rss"><img src="https://agentmods.dev/badge/skills/yusufkaraaslan/skill_seekers/rss.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.00012 | $0.00879 |
| Opus 5 | $0.00006 | $0.00439 |
| Sonnet 5 | $0.00002 | $0.00176 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade A, and why
golden-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 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Example Engineering Blog Feed Skill
Use when testing the rss golden build
📡 Feed Information
Feed Title: Example Engineering Blog
Feed Type: RSS 2.0
Website: https://example.com
Language: en-us
Description: A feed description that is intentionally longer than the three hundred character limit applied in the Feed Information block of SKILL.md. A feed description that is intentionally longer than the three hundred character limit applied in the Feed Information block of SKILL.md. A feed description th...
Generator: ExampleCMS 2.0
Rights: © Example Inc.
💡 When to Use This Skill
Use this skill when you need to:
- Reference articles and content from Example Engineering Blog
- Look up specific topics covered in the feed
- Find author perspectives and expert analysis
- Review recent posts and updates on the subject
- Explore categorized content by tags or topics
📖 Article Overview
Total Articles: 4
Content by Category:
- Dev Ops: 1 articles
- Python: 1 articles
- uncategorized: 1 articles
- ★★★: 1 articles
📰 Recent Articles
Continuous Delivery in Practice
Published: Mon, 01 Jan 2024 10:00:00 GMT | Author: Jane Doe
This is a deliberately long summary that keeps going well past the two hundred character truncation threshold used by the recent-articles block of SKILL.md so that the shortened form with a trailing e...
Typing Tips for Python
Published: Fri, 15 Mar 2024 08:30:00 GMT | Author: John Roe
Short notes on gradual typing.
An Uncategorized Note
Author: Jane Doe
A note without tags.
Symbols Only
Published: Sat, 10 Feb 2024 12:00:00 GMT
✍️ Authors (2)
- Jane Doe: 2 articles
- John Roe: 1 articles
🏷️ Tags (55)
Dev Ops, Python, dev-ops, tag00, tag01, tag02, tag03, tag04, tag05, tag06, tag07, tag08, tag09, tag10, tag11, tag12, tag13, tag14, tag15, tag16, tag17, tag18, tag19, tag20, tag21, tag22, tag23, tag24, tag25, tag26, tag27, tag28, tag29, tag30, tag31, tag32, tag33, tag34, tag35, tag36, tag37, tag38, tag39, tag40, tag41, tag42, tag43, tag44, tag45, tag46 ... and 5 more
What ships with it
5 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 · 109 lines · 12 tokens per session scan A f82f092ee76a
golden-rss is a skill published in the GitHub repository yusufkaraaslan/Skill_Seekers (14,895 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 879 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-30.
Other skills, from other repositories
octocode-chrome-devtools
Use when a live page needs Chrome DevTools/CDP evidence: network failures, console errors, performance, DOM/CSS actionability, screenshots/PDF, cookies/storage, click/fill/search, HAR, or auth-gated pages. Phrases like debug in Chrome, live page health, CDP snapshot, cookie bridge. Not for static crawl or bulk extract…
octocode-graph-eval
Use when you need a measurable keep/discard loop — goal→KPI, baseline vs target, held-out checks, eval suites, or don't-stop-till-done against a runnable sensor. Not for ordinary ship checks where 'tests passed' is enough.
octocode-subagent
Use when spawning workers or offloading work: Task/subagents, specialist handoffs, A2A peers, sealed packets, coordinate/synthesize, challenge techniques (rubber-duck, interview, mimic-flow, red-team, blind review, consensus), or local Ollama one-shots to save tokens. Measuring keep/discard KPIs → octocode-graph-eval.
octocode-brainstorming
Use when an idea needs disciplined exploration before building: generate options, test whether it is worth building, map adjacent solutions, challenge assumptions, narrow scope, or choose Build RFC / Prototype / Narrow / Park — even if nobody said brainstorm. Already decided to implement a specific plan → skip.
octocode-scraping
Use when extracting or mapping public web content into a local cited corpus: scrape or crawl a URL/docs site, pull tables/pricing/product fields, diagnose blocked or thin pages, or answer from saved pages. Phrases like scrape this URL, crawl the docs, build a corpus, extract pricing. Prefer keyless fetch; ask before…
octocode-roast
Use when code needs a blunt evidence-backed roast or memorable critique: smell inventory, debt ranking, hot-path autopsy, savage/diff review, security or performance sins, or practical redemption paths. Phrases like roast this, brutal review, top sins, cleanup debt. Polite evidence-first PR review → octocode-research.