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/tarampampam/webhook-tester/agents-mdgit clone --depth 1 https://github.com/tarampampam/webhook-testerWrote 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/instructions/tarampampam/webhook-tester/agents-md)<a href="https://agentmods.dev/instructions/tarampampam/webhook-tester/agents-md"><img src="https://agentmods.dev/badge/instructions/tarampampam/webhook-tester/agents-md.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.01353 | $0.01353 |
| Opus 5 | $0.00677 | $0.00677 |
| Sonnet 5 | $0.00271 | $0.00271 |
| Haiku 4.5 | $0.00135 | $0.00135 |
Grade A, and why
webhook-tester AGENTS.md 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS - Project Rules
Read this file AND the global rules before making any code changes - https://tarampampam.github.io/.github/ai/AGENTS.md (mirror - https://raw.githubusercontent.com/tarampampam/.github/refs/heads/master/ai/AGENTS.md).
Instruction Priority
- This file (
AGENTS.mdin this repository) - Global rules (external URLs)
- Other documentation
If rules conflict, follow the highest priority source.
Project Overview
webhook-tester is a web application for testing and debugging webhooks. It consists of:
- Go backend (
cmd/,internal/) - HTTP API server, storage (in-memory/Redis/fs), WebSocket, ngrok tunnel support - TypeScript/React frontend (
web/src/) - Vite-based SPA (React + Mantine UI + openapi-fetch) - OpenAPI spec (
api/openapi.yml) - source of truth for the HTTP API contract
Go module: gh.tarampamp.am/webhook-tester/v2
Architecture
cmd/webhook-tester/ - CLI entrypoint (urfave/cli/v3)
internal/
cli/ - CLI command implementations
http/
handlers/ - one file per OpenAPI operation
middleware/ - HTTP middleware
openapi/ - generated server stubs (do not edit *.gen.*)
server.go - HTTP server wiring
storage/ - storage.go defines the interface; inmemory.go / redis.go / fs.go implement it
pubsub/ - pub/sub interface + memory/redis implementations (WebSocket notifications)
tunnel/ - ngrok tunnel integration
logger/ - zap logger setup
web/
src/
api/ - schema.gen.ts (generated) + openapi-fetch client
screens/ - page-level React components (home, session, not-found)
shared/ - reusable components, hooks, utils, providers
routing/ - route definitions
db/ - client-side IndexedDB (Dexie) for local state
api/openapi.yml - OpenAPI 3.x spec (source of truth for all HTTP routes)
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.
- 4d ago First seen · 133 lines · 1,353 tokens per session scan A 76c1e5366fe2
webhook-tester AGENTS.md is an instructions file published in the GitHub repository tarampampam/webhook-tester (531 stars, last pushed 2d ago), licensed MIT. It adds 1,353 tokens to every session, about $0.0068 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-30.
Other instructions, from other repositories
ollama CLAUDE.md
Claude Code instructions for ollama/ollama: See AGENTS.md for the shared agent instructions for this repository.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.
gorest AGENTS.md
AGENTS.md instructions for pilinux/gorest, covering agents.md, project overview, build and run commands, build and tidy dependencies.
kessoku AGENTS.md
AGENTS.md instructions for mazrean/kessoku, covering repository guidelines — kessoku, project structure, common commands, build and test.
ketch CLAUDE.md
Claude Code instructions for 1broseidon/ketch, covering ketch, architecture, build & test, output format and output flags (all commands).
coral CLAUDE.md
Instructions for cdknorow/coral, covering claude.md - coral go, mission, testing, go unit tests and legacy parity tools (historical reference).