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.
git clone --depth 1 https://github.com/MadAppGang/magusWrote 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/commands/madappgang/magus/http-service)<a href="https://agentmods.dev/commands/madappgang/magus/http-service"><img src="https://agentmods.dev/badge/commands/madappgang/magus/http-service/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/commands/madappgang/magus/http-service"><img src="https://agentmods.dev/badge/commands/madappgang/magus/http-service.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.00027 | $0.00269 |
| Opus 5.5 | $0.00011 | $0.00108 |
| Sonnet 5.5 | $0.00005 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
http-service 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 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.
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.
What it actually says
<user_request>$ARGUMENTS</user_request>
- Read
skills/http-service/SKILL.mdin full first, resolved against this plugin's own directory (the tree this command was loaded from). It is the router: it names which files inskills/http-service/references/your task actually needs. Read those too before writing code.
Use this for any Bun HTTP server, JSON API, route handler, middleware or response-shape work.
- Copy
skills/http-service/assets/http/into the project rather than retyping middleware. Four measured routing behaviours will otherwise bite you — in particular a method map does not produce a 405, andserver.reload()replaces the whole route table. - Before reporting done:
bun testandtsc --noEmitclean, every route has an explicit method allow-list,maxRequestBodySizeis set, and no hand-builtnew Response(JSON.stringify(…))bypasses the response helpers.
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 · 21 lines · 27 tokens per session scan A 411954de2660
http-service is a command published in the GitHub repository MadAppGang/magus (13 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 269 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
cloudflare-durable-objects:debug
Interactive Durable Objects debugging workflow. Diagnoses common DO errors, configuration issues, and runtime problems with step-by-step troubleshooting.
cloudflare-durable-objects:optimize
Interactive Durable Objects performance optimization assistant. Analyzes existing DO code and provides specific optimization recommendations with implementation guidance.
doctor
Diagnose the PyWry install (Python interpreter, pywry[mcp] extra, native binary, MCP server reachability).
api
Debug API and data flow issues by tracing through Component -> TanStack Query -> Hono Route -> Service -> SQLite/JSONL.
optimize-code
Analyze and optimize code for performance, efficiency, and scalability.
dev-error-handling
Implements a robust and consistent error handling strategy.