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 AgentComputerAI/torch --skill githubgit clone --depth 1 https://github.com/AgentComputerAI/torchWrote 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/agentcomputerai/torch/github)<a href="https://agentmods.dev/skills/agentcomputerai/torch/github"><img src="https://agentmods.dev/badge/skills/agentcomputerai/torch/github/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/agentcomputerai/torch/github"><img src="https://agentmods.dev/badge/skills/agentcomputerai/torch/github.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.00063 | $0.01151 |
| Opus 5.5 | $0.00025 | $0.00460 |
| Sonnet 5.5 | $0.00013 | $0.00230 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
github scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Phase 0 curl → done. Data is in raw HTML, no protection headers, no JS required. Skip browser entirely. How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub (github.com)
GitHub's public HTML pages are fully server-rendered with no JS gating and no bot protection on unauthenticated GETs. A one-shot
fetch+ cheerio parse is all you need. Only reach for the REST API (api.github.com) when you hit the 60 req/hr unauthenticated limit or need structured fields (topics, license, default branch) not present on the HTML.
Detection
| Signal | Value |
|---|---|
| CDN | GitHub edge (Varnish/Fastly) |
| Framework | Rails + Turbo, React islands |
| Anti-bot | None on public pages |
| Auth | Optional — anon works |
| Rate limit (HTML) | Generous, IP-based, soft |
| Rate limit (REST) | 60/hr unauth, 5000/hr with token |
Architecture
/trendingis a normal Rails view. Repo cards are<article class="Box-row">inside<div data-hpc>.- Note: the trending list size varies — historically 25, but currently GitHub often returns only ~10 cards. Don't hardcode the count.
- Repo pages (
/{owner}/{name}) have data in multiple places: HTML meta tags,<react-app>embedded JSON payloads, and DOM nodes. For simple fields (stars, forks, description), raw DOM is easiest. - Sitemaps at
/sitemap.xmlare huge — prefer targeted URL lists.
Strategy used
Phase 0 curl → done. Data is in raw HTML, no protection headers, no JS required. Skip browser entirely.
Extraction (trending)
import { load } from 'cheerio';
const res = await fetch('https://github.com/trending', {
headers: { 'User-Agent': 'Mozilla/5.0' },
});
const $ = load(await res.text());
$('article.Box-row').each((_, el) => {
const $el = $(el);
const fullName = $el.find('h2 a').attr('href').replace(/^\//, '').replace(/\s+/g, '');
const description = $el.find('p').text().trim() || null;
const language = $el.find('[itemprop="programmingLanguage"]').text().trim() || null;
const stars = parseInt($el.find('a[href$="/stargazers"]').text().trim().replace(/,/g, '')) || 0;
const forks = parseInt($el.find('a[href$="/forks"]').text().trim().replace(/,/g, '')) || 0;
const starsToday = $el.find('span.d-inline-block.float-sm-right').text().trim().replace(/\s+/g, ' ');
// ...
});
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.
- 1mo ago First seen · 105 lines · 63 tokens per session scan A f6796d9f6be2
github is a skill published in the GitHub repository AgentComputerAI/torch (5 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 1,151 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
chrome-extension
Use when building or shipping a Manifest V3 browser extension and hitting its quirks — service worker dying and losing state, permission warnings, a Chrome Web Store rejection, content-script/worker/popup messaging, or an MV2-to-V3 migration. NOT a generic web app (that is nextjs), NOT a desktop shell (that is…
data-scraper
Use when data lives on a website with no usable API — listings, prices, public records — and the scrape must stay legal and not get blocked: legal gate, extraction path, durable selectors, pacing, resilience. NOT parsing bytes you already hold into fields (that is structured-extraction), NOT a documented API or key…
nodejs
Use when building or operating a plain Node.js / Express 5 backend service: project layout, async correctness, central error middleware, fail-fast config, graceful shutdown on SIGTERM. NOT DI modules/providers/guards (that is nestjs), NOT the type system or tsconfig (that is typescript), NOT REST contract design (that…
checking-a-page
Check that a web page you wrote or changed actually works, by opening it in a browser and driving every control on it. Use after creating or editing an HTML page, or the JavaScript or CSS that a page loads.
browser-qa
Testing web apps through a real browser: reconnaissance before acting, selector discovery, state capture, console errors and screenshot evidence. Use on a web surface end to end, or to reproduce a front-end bug.
browser-automation
A browser-automation workflow that detects the terminal environment and chooses a browser control tool. It supports opening pages, taking snapshots, clicking, filling fields, and other checks.