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/forest/agent-skills/req-api-clientnpx skills add forest/agent-skills --skill req-api-clientgit clone --depth 1 https://github.com/forest/agent-skillsWhat 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.00062 | $0.03590 |
| Opus 5 | $0.00031 | $0.01795 |
| Sonnet 5 | $0.00012 | $0.00718 |
| Haiku 4.5 | $0.00006 | $0.00359 |
Grade A, and why
req-api-client 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building API Clients (SDKs) with Req
Overview
Build "Small Development Kits" — minimal, composable API wrappers using Req's plugin architecture instead of massive auto-generated SDKs. The core insight from Dashbit: most apps use 2-3 API calls, not 400 modules.
When to Use
- Building a wrapper around any REST/HTTP API
- Creating a reusable service client (Stripe, S3, GitHub, etc.)
- Integrating with an external service that needs auth, retries, or custom headers
- Adding webhook signature verification
When NOT to use: If a well-maintained Elixir SDK already exists and covers your needs, use it.
Core Pattern: The Module Wrapper
Every API client follows the same new/request/request! shape:
defmodule MyApp.Stripe do
@doc "Build a configured Req struct. Call with options to override defaults."
def new(options \\ []) when is_list(options) do
config = Application.fetch_env!(:my_app, :stripe)
Req.new(
base_url: "https://api.stripe.com/v1",
auth: {:bearer, Keyword.fetch!(config, :api_key)},
retry: :transient
)
|> Req.Request.append_request_steps(
stripe_post: fn req ->
# Stripe uses POST for writes — auto-convert GET with body
with %{method: :get, body: <<_::binary>>} <- req do
%{req | method: :post}
end
end
)
|> Req.merge(Keyword.get(config, :req_options, []) ++ options)
end
def request(url_or_opts, options \\ [])
def request(url, options) when is_binary(url),
do: Req.request(new([url: parse_url(url)] ++ options))
def request(options, _) when is_list(options),
do: Req.request(new(options))
def request!(url_or_opts, options \\ [])
def request!(url, options) when is_binary(url),
do: Req.request!(new([url: parse_url(url)] ++ options))
def request!(options, _) when is_list(options),
do: Req.request!(new(options))
# Smart URL routing via pattern matching on resource IDs
defp parse_url("cus_" <> _ = id), do: "/customers/#{id}"
defp parse_url("sub_" <> _ = id), do: "/subscriptions/#{id}"
defp parse_url("/" <> _ = path), do: path
defp parse_url(path), do: "/" <> path
end
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.
- yesterday First seen · 399 lines · 62 tokens per session scan A 475f11827d3f
req-api-client is a skill published in the GitHub repository forest/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 62 tokens to every session and 3,590 once invoked, about $0.0003 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.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…