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/imoonkey/openweb/guardiannpx skills add imoonkey/openweb --skill guardiangit clone --depth 1 https://github.com/imoonkey/openwebWhat 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.00000 | $0.00397 |
| Opus 5 | $0.00000 | $0.00198 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
guardian 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 2d 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
The Guardian
Overview
Major UK/international news outlet. Open public REST API at content.guardianapis.com for searching articles, fetching full content, and browsing section feeds.
Workflows
Search for articles on a topic
searchArticles(q)→id, webTitle, sectionId, webPublicationDategetArticle(ids=id)→ fields.body, fields.headline, fields.byline
Browse latest news in a section
getSectionFeed(section)→id, webTitle, webPublicationDategetArticle(ids=id)→ full article body
Research a topic across sections
searchArticles(q, order-by: newest)→ recent coveragegetSectionFeed(section)→ compare coverage across sections
Operations
| Operation | Intent | Key Input | Key Output | Notes |
|---|---|---|---|---|
| searchArticles | find articles by keyword | q | id, webTitle, sectionId, webPublicationDate, fields | entry point, paginated |
| getArticle | full article content | ids <- searchArticles / getSectionFeed | fields.body, fields.headline, fields.byline | body is HTML |
| getSectionFeed | latest in a section | section | id, webTitle, webPublicationDate, fields | defaults to newest first |
Quick Start
# Search for articles
openweb guardian exec searchArticles '{"q": "artificial intelligence"}'
# Get a specific article (use id from search results)
openweb guardian exec getArticle '{"ids": "technology/2025/dec/10/police-facial-recognition-technology-bias"}'
# Get latest technology articles
openweb guardian exec getSectionFeed '{"section": "technology"}'
# Get latest world news
openweb guardian exec getSectionFeed '{"section": "world"}'
What ships with it
8 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.
- 2d ago First seen · 43 lines · 0 tokens per session scan A a7e93ee6d0d2
guardian is a skill published in the GitHub repository imoonkey/openweb (58 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 397 tokens. 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
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…