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 press-pass/journalism-skills --skill add-ai-access-scrapersgit clone --depth 1 https://github.com/press-pass/journalism-skillsWrote 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/press-pass/journalism-skills/add-ai-access-scrapers)<a href="https://agentmods.dev/skills/press-pass/journalism-skills/add-ai-access-scrapers"><img src="https://agentmods.dev/badge/skills/press-pass/journalism-skills/add-ai-access-scrapers/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/press-pass/journalism-skills/add-ai-access-scrapers"><img src="https://agentmods.dev/badge/skills/press-pass/journalism-skills/add-ai-access-scrapers.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.00025 | $0.00384 |
| Opus 5 | $0.00013 | $0.00192 |
| Sonnet 5 | $0.00005 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
add-ai-access-scrapers 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 12d 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
Call the get_ai_access_sources MCP tool to get all AI Access sources with more than 10 scrape items.
For each source returned, read its aiAccessInstructions and sourceClientKey to understand what data it accesses and how. Then:
-
Read
backend/api/services/source/source_service.pyto see the currentperform_scrape_for_sourcefunction and its existing patterns (REDDIT, TWITTER, NYC_OPEN_DATA, AI_ACCESS). -
For each source, determine if you can replace the generic AI Access scraping with a dedicated client that fetches the data directly (e.g., via an API, RSS feed, or structured web request). Skip sources whose instructions describe access patterns that cannot be replicated without Claude (e.g., "search the web for..." or "navigate through a complex UI").
-
For each source you can write a dedicated scraper for: a. Create a new client module in
backend/api/services/source/that fetches the data. b. Create a new SourceAccessType choice in the backend and a migration. b. Add anelifbranch inperform_scrape_for_sourcethat checkssource.source_access_type == SourceAccessTypeand calls your new client, creating ScrapeItem records from the response. c. Place the new branch before the genericelif source.source_access_type == SourceAccessType.AI_ACCESSbranch so it takes priority. -
Create a git branch, commit the changes, and open a PR. In the PR description, list each source ID and what dedicated scraper was added for it.
If no sources can be converted to dedicated scrapers, report which sources were found and why they could not be converted.
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.
- 12d ago First seen · 20 lines · 25 tokens per session scan A 075550cb292b
add-ai-access-scrapers is a skill published in the GitHub repository press-pass/journalism-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 384 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…