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 huggingfacegit 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/huggingface)<a href="https://agentmods.dev/skills/agentcomputerai/torch/huggingface"><img src="https://agentmods.dev/badge/skills/agentcomputerai/torch/huggingface/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/huggingface"><img src="https://agentmods.dev/badge/skills/agentcomputerai/torch/huggingface.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.00105 | $0.01613 |
| Opus 5.5 | $0.00042 | $0.00645 |
| Sonnet 5.5 | $0.00021 | $0.00323 |
| Haiku 4.5 | $0.00011 | $0.00161 |
Grade A, and why
huggingface 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):** HTML returns 200 but the data lives in a hydration blob. Not worth parsing — instead checked `/api/models?pipeline_tag=text-generation&sort=trendingScore`. Got clean JSON. Done. How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hugging Face (huggingface.co)
The model/dataset/space listing HTML pages are server-rendered behind CloudFront but there is no reason to scrape them — Hugging Face ships a public JSON API that backs the same UI and accepts every URL filter verbatim. One-to-one parameter mapping, no auth, no rate-limit in practice (a soft ratelimit: "pages";q=100;w=300 is on the HTML routes, not /api).
Detection
| Signal | Value |
|---|---|
| CDN | CloudFront (x-cache: ... cloudfront.net) |
| Framework | SvelteKit (huggingface-moon) |
| Anti-bot | None on /api/*. HTML pages have a soft page rate limit. |
| Auth | Not required for public models/datasets/spaces. |
| robots.txt | Allows /api/ crawling. |
Architecture
Every listing URL https://huggingface.co/models?<filters> has a direct JSON twin at https://huggingface.co/api/models?<same filters>. The HTML page is just a SvelteKit shell that calls the same endpoint client-side.
- Endpoint:
https://huggingface.co/api/models - Filters map 1:1:
pipeline_tag,library,language,license,other,search,author,filter. - Sort:
sort=trendingScore|downloads|likes|createdAt|lastModified+direction=-1|1. - Page size:
limit(max 100 observed, use 100). - Pagination: cursor-based via the
Linkresponse header (<...cursor=...>; rel="next"). Extract thecursorquery param from that URL and pass it to the next request.
Also available:
/api/datasets— same shape, for /datasets listings./api/spaces— same shape, for /spaces listings./api/models/<repo_id>— full model card metadata for a single repo.
Strategy used
- Phase 0 (curl): HTML returns 200 but the data lives in a hydration blob. Not worth parsing — instead checked
/api/models?pipeline_tag=text-generation&sort=trendingScore. Got clean JSON. Done. - Phase 1–2: skipped.
Stealth config that works
None needed. Plain fetch with a generic User-Agent.
await fetch("https://huggingface.co/api/models?...", {
headers: { "User-Agent": "Mozilla/5.0 torch-scraper" },
});
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 · 142 lines · 0 tokens per session scan A 9f790732e877
huggingface is a skill published in the GitHub repository AgentComputerAI/torch (5 stars, last pushed 6mo ago), licensed MIT. It adds 105 tokens to every session and 1,613 once invoked, about $0.0004 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.