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 instructions/mtford90/httap/agents-mdgit clone --depth 1 https://github.com/mtford90/httapWhat 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.03080 | $0.03080 |
| Opus 5 | $0.01540 | $0.01540 |
| Sonnet 5 | $0.00616 | $0.00616 |
| Haiku 4.5 | $0.00308 | $0.00308 |
Grade A, and why
httap AGENTS.md 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.
**Examples**: `src/daemon/storage.test.ts`, `src/cli/tui/utils/curl.test.ts`, `src/daemon/proxy.test.ts` How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
httap - Terminal HTTP Interception Toolkit
Planning & Status
docs/PLAN.md is the source of truth for all development work on this project.
- Always check
docs/PLAN.mdbefore starting work to understand current priorities - Update
docs/PLAN.mdwhen completing tasks (move to Completed section) - Update
docs/PLAN.mdwhen discovering new tasks or requirements - Keep task descriptions concise but informative
- Code reviews are stored in
docs/reviews/<date>/
Published to npm as httap (v0.1.0). The name httap was taken.
Project Overview
httap is a terminal-based HTTP interception/inspection tool with project-scoped isolation and a lazygit-style TUI. It captures HTTP/HTTPS traffic through a MITM proxy and displays it in an interactive terminal interface.
Product Vision
Messaging Pillars
These define what httap is and how it should feel — keep them in mind when making design and UX decisions:
- Workspace-isolated — per-project
.httap/directory, no cross-project bleed - Lives in your terminal — TUI, not another GUI app; fits your existing workflow
- AI-native — MCP integration, AI writes your mocks, inspects your traffic
- Config-as-code — mocks and interceptors are TypeScript files, not GUI toggles
- Zero-config —
httap onand go; auto-starts daemon, auto-generates certs - Developer-first — built for how you already work, not bolted on
Strategic Direction
The long-term vision centres on mocks & interceptors as code — TypeScript config files inside .httap/ that define middleware/intercept/mock behaviour, with full programmatic access to the httap client. The TUI visualises what's configured, but logic lives in code.
MCP integration is a first-class concern: AI agents should be able to discover .httap, communicate with the proxy, search through captured traffic, and write/manage mock rules via the config-as-code system.
CLI Design Philosophy — Gradual Discovery
The CLI follows a gradual discovery pattern — each command's output hints at what you can do next, so usage builds on itself naturally:
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 · 261 lines · 3,080 tokens per session scan A 7a9d0a905ebb
httap AGENTS.md is an instructions file published in the GitHub repository mtford90/httap (8 stars, last pushed 6mo ago), licensed MIT. It adds 3,080 tokens to every session, about $0.0154 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-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.