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/fredoliveira/agents/summarize-urlsnpx skills add fredoliveira/agents --skill summarize-urlsgit clone --depth 1 https://github.com/fredoliveira/agentsWrote 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/fredoliveira/agents/summarize-urls)<a href="https://agentmods.dev/skills/fredoliveira/agents/summarize-urls"><img src="https://agentmods.dev/badge/skills/fredoliveira/agents/summarize-urls.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.1 | $0.00035 | $0.00636 |
| Opus 5 | $0.00017 | $0.00318 |
| Sonnet 5 | $0.00007 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
summarize-urls 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 6d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summarize URLs
Purpose
Turn a batch of URLs -- typically exported from OneTab or a similar browser extension -- into a curated, Obsidian-friendly markdown summary. Each link is fetched, read, and distilled into a short description so the list becomes a useful reference note rather than a wall of raw URLs.
Instructions
1. Parse the input
The user will paste a list of URLs. Each line can be in one of these formats:
| Format | Example |
|---|---|
url | title |
https://example.com | Example Site |
url | title | source |
https://example.com | Example Site | Hacker News |
| bare URL | https://example.com |
- Split on
\|(pipe surrounded by spaces) to separate URL from title/source. - Ignore blank lines.
- If a title is present, use it as the display name; otherwise derive one from the page content.
2. Fetch and summarize each URL
For each URL:
- Fetch the page content using WebFetch.
- Ask WebFetch to extract: what the page is about in 1-2 sentences, and any key takeaways.
- If a URL is unreachable (localhost, paywalled, 404, etc.), note it as
(could not fetch)and use the title if available.
Fetch multiple URLs in parallel where possible to save time.
3. Build the markdown summary
Structure the output as:
## Link Summary
| Link | Summary |
| --- | --- |
| [Display Title](url) | 1-2 sentence summary |
| ... | ... |
If there are more than 5 links and clear thematic clusters emerge (e.g. "AI / Agents", "Web Dev", "Security"), group them under subheadings instead of a single flat table:
## Link Summary
### AI / Agents
| Link | Summary |
| --- | --- |
| ... | ... |
### Web Dev
| Link | Summary |
| --- | --- |
| ... | ... |
4. Append to the daily note
- Find the Obsidian vault path by running
obsidian vault. - Append the markdown summary to the daily note by running:
obsidian daily:append content="<the full markdown summary>" silent
- Escape any double quotes in the content so the shell command works.
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.
- 6d ago First seen · 86 lines · 35 tokens per session scan A b40bafe81d5c
summarize-urls is a skill published in the GitHub repository fredoliveira/agents (24 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 636 once invoked, about $0.0002 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
create-custom-grader
Use when converting an existing benchmark, rubric, verifier, task YAML/JSON, or domain check into SkillEvaluator BYOG/BYOT custom evaluation.
simple
Summarize short user notes into clear action items.
agent-ready-cloudflare
Audit and improve website readiness for AI agents using the Cloudflare "Is It Agent Ready?" scanner (isitagentready.com). Covers scanning via API, interpreting results, generating implementation prompts, and fixing every check. Use when the user mentions "agent ready", "isitagentready", "AI agent scan", "agent…
aidlc-master
Runs the AWS AI-DLC (AI-Driven Development Life Cycle) methodology end to end: an adaptive three-phase workflow (Inception → Construction → Operations) with human approval gates, a full audit trail, and all artifacts in aidlc-docs/. Use when the user says "Using AI-DLC", "AI-DLC", "AIDLC", "aidlc-master", or asks for…
security-specialist
Runs security audits on codebases — full scans, diff reviews, threat models, vulnerability triage, remediation guidance, and finding tracking. Activate when the user says "security scan", "audit this repo", "review this PR for security", "threat model", "triage vulnerabilities", "fix this vuln", or "track findings".
ralph-loop-kiro-specs
Automated iterative agent runner for spec-based development in Kiro. Wraps kiro-cli in a self-correcting bash loop that picks up tasks from a Kiro spec, implements them one at a time, verifies against exit criteria, and accumulates corrections and codebase patterns across iterations. Use this skill when the user…