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/fisker086/aiops/http_clientnpx skills add fisker086/AIOps --skill http_clientgit clone --depth 1 https://github.com/fisker086/AIOpsWhat 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.00021 | $0.00427 |
| Opus 5 | $0.00010 | $0.00214 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
http-client 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
activation_keywords: [http, request, api, curl, get, post, put, delete, webhook, fetch, url] What it actually says
HTTP Client Skill
Provides full HTTP client capabilities beyond simple URL fetching:
- Support all HTTP methods: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
- Custom headers and query parameters
- JSON and form-encoded request bodies
- Response status, headers, and body inspection
- Automatic text extraction: HTML pages are automatically stripped of tags and converted to readable text
Use builtin_http_client tool with fields:
method: HTTP method (GET, POST, PUT, PATCH, DELETE, etc.)url: the target URL (https only)headers: (optional) JSON object of headersbody: (optional) request body stringcontent_type: (optional) content type for body (default: application/json)
Note: Private/local hosts are blocked for security.
When to use HTTP Client vs Browser
- Prefer
builtin_http_clientfor calling HTTPS APIs, webhooks, and reading page-like URLs where a single GET/POST and HTML → text (or raw body) is enough. No DOM, no in-page clicks, no JavaScript rendering in a browser engine. - Use
builtin_browser(skillbuiltin_skill.browser_client) only on the AI TaskMeta desktop: it opens a visible Chrome and uses CDP (navigate, DOM actions, text for the model). It is not headless and not server-side HTTP. For API-only fetch, usebuiltin_http_client. The API server does not run desktop browser tools. - Summary: HTTP Client = server-side HTTPS fetch; Browser = desktop visible Chrome automation. Prefer HTTP when a single request and HTML/body text is enough.
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 · 31 lines · 21 tokens per session scan A 187432bc4fe0
http-client is a skill published in the GitHub repository fisker086/AIOps (21 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 427 once invoked, about $0.0001 per session on Opus 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.