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/jjmartres/ai-coding-agents/httpienpx skills add jjmartres/ai-coding-agents --skill httpiegit clone --depth 1 https://github.com/jjmartres/ai-coding-agentsWrote 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/jjmartres/ai-coding-agents/httpie)<a href="https://agentmods.dev/skills/jjmartres/ai-coding-agents/httpie"><img src="https://agentmods.dev/badge/skills/jjmartres/ai-coding-agents/httpie.svg" alt="Measured on agentmods" 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 | $0.00148 | $0.01901 |
| Opus 5 | $0.00074 | $0.00950 |
| Sonnet 5 | $0.00030 | $0.00380 |
| Haiku 4.5 | $0.00015 | $0.00190 |
Grade C, and why
httpie scanned grade C with 3 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 3d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
| POST JSON | `http POST url key=val` | `curl -X POST -H 'Content-Type: application/json' -d '{"key":"val"}' url` | Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt install httpie Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
## HTTPie vs curl Equivalents How it starts
The opening of the file, as written. The whole thing — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HTTPie CLI Skill
HTTPie is a modern, human-friendly HTTP client for the command line. The main command is http (or https for HTTPS-only).
Installation
# pip (recommended)
pip install httpie
# brew (macOS)
brew install httpie
# apt (Debian/Ubuntu)
sudo apt install httpie
Verify: http --version
Request Syntax
http [METHOD] URL [REQUEST_ITEMS...]
- METHOD is optional: defaults to
GETwhen no data,POSTwhen data is present - URL: scheme defaults to
http://; use:3000as shorthand forlocalhost:3000
Request Items � Key Separators
| Separator | Type | Example |
|---|---|---|
= |
JSON string field (or form field with -f) |
name=Jean |
:= |
Raw JSON value (non-string) | active:=true, count:=42, tags:='["a","b"]' |
== |
URL query parameter | search==httpie |
: |
HTTP header | Authorization:Bearer TOKEN |
@ |
File upload (form/multipart) | file@./report.pdf |
=@ |
File content as string field | body=@./message.txt |
:=@ |
File content as raw JSON | config:=@./config.json |
Common Examples
GET requests
# Simple GET
http GET https://api.example.com/users
# With query params
http GET https://api.example.com/users search==alice limit==10
# Shorthand (method inferred)
http https://api.example.com/users
# Localhost shorthand
http :8080/health
POST with JSON (default)
# String and non-string fields
http POST https://api.example.com/users \
name="Jean-Jacques" \
email="[email protected]" \
active:=true \
roles:='["admin","user"]'
# Inline raw JSON body (pipe it in)
echo '{"name":"test"}' | http POST https://api.example.com/users
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.
- 3d ago First seen · 279 lines · 148 tokens per session scan C 0b994905dd0e
httpie is a skill published in the GitHub repository jjmartres/ai-coding-agents (43 stars, last pushed 2mo ago), licensed MIT. It adds 148 tokens to every session and 1,901 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it C with 3 findings (sends data to an external url, asks for root, 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
cocowatch
Developer engagement observer — non-blocking, always-on observational layer that tracks Delegation Intensity, Review Depth, and Engagement Zone throughout a session. Summary surfaced at $ship and FULL checkpoints.
audit
Eight audit modes (codebase — owns "audit the codebase" — docs/process, performance, threat-model, motion, SEO, debt). Triggers "nuclear review", "whole codebase review", "adversarial audit", "fable audit", "correctness audit", "audit the docs", "doc drift", "process audit", "perf audit", "why is it slow", "bundle…
the-grilling
Use when adversarial brainstorming is needed after reconnaissance — the Proposer, Devils-Advocate, and Synthesizer each run ONE pass (no rounds); the Don is grilled on the IDEA first, one question at a time, then the proposal is attacked.
using-gangsta
Use when starting any conversation — establishes how to find and use Gangsta skills, enforces the 1% invocation rule, maps platform tools, and routes the Don's intent through the Gangsta Agents Family hierarchy.
lighthouse
Lighthouse audit + improvement loop until targets met. Triggers "lighthouse", "page speed", "improve scores", "LCP", "CLS", "INP", "core web vitals". Repo-wide perf audits ("perf audit") go to /audit performance mode instead.
interrogation-debugging
Use when encountering any bug, test failure, or unexpected behavior — finds the rat in the code through systematic root-cause interrogation before any fix attempts.