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/lestrrat-go/jwx/agents-mdgit clone --depth 1 https://github.com/lestrrat-go/jwxWrote 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/lestrrat-go/jwx/agents-md)<a href="https://agentmods.dev/instructions/lestrrat-go/jwx/agents-md"><img src="https://agentmods.dev/badge/instructions/lestrrat-go/jwx/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.03058 | $0.03058 |
| Opus 5 | $0.01529 | $0.01529 |
| Sonnet 5 | $0.00612 | $0.00612 |
| Haiku 4.5 | $0.00306 | $0.00306 |
Grade A, and why
jwx 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
For Module Consumers
If you are writing code that uses jwx (not developing jwx itself):
- Examples: See
github.com/jwx-go/examplesfor runnable usage patterns (locally atexamples/when checked out viago.work) - Documentation: See
docs/directory and package READMEs - API Reference: Use
go docor https://pkg.go.dev/github.com/lestrrat-go/jwx/v4 - Migrating from v3? See
MIGRATION.mdfor a complete guide, andgithub.com/jwx-go/jwxmigratefor machine-readable migration rules and automated checking
The rest of this document focuses on developing the jwx library itself.
Go Version
This project requires Go 1.26.0 or later. Check go.mod for the exact version.
GOEXPERIMENT
v4 depends on encoding/json/v2, which is behind GOEXPERIMENT=jsonv2 on Go 1.26 and part of the standard library from Go 1.27 on. The Makefile probes the toolchain and rewrites GOEXPERIMENT to match it, adding jsonv2 on Go 1.26 and removing it on Go 1.27, so make targets work on both even when your shell already exports the variable. Experiments other than jsonv2 are left alone. scripts/test-companion.sh carries the same probe.
A direct go build, go test, or go run invocation on Go 1.26 must set it:
GOEXPERIMENT=jsonv2 go test ./...
GOEXPERIMENT=jsonv2 go build ./...
Without this, Go 1.26 builds fail with build constraints exclude all Go files errors.
On Go 1.27 do not set it. Naming an experiment the toolchain already ships for real rebuilds the standard library under a non-default configuration for no benefit.
Module Path vs Physical Layout
This repository uses a flat layout with vanity import paths. There is no physical v4/ directory.
| Branch | Module Path | Physical Root |
|---|---|---|
develop/v4 |
github.com/lestrrat-go/jwx/v4 |
/ (repo root) |
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 · 281 lines · 3,058 tokens per session scan A 66abdef07afa
jwx AGENTS.md is an instructions file published in the GitHub repository lestrrat-go/jwx (2,420 stars, last pushed today), licensed MIT. It adds 3,058 tokens to every session, about $0.0153 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 AGENTS.md
AGENTS.md instructions for ollama/ollama, covering agents.md and building.
awesome-go AGENTS.md
AGENTS.md instructions for avelino/awesome-go, covering awesome-go · llm contribution guide, project snapshot, when modifying the awesome list, coding guidelines and testing & validation.
go-micro CLAUDE.md
Claude Code instructions for micro/go-micro, covering claude.md - go micro project guide, project overview, build & test, run all tests and run tests for a specific package.
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-examples.instructions.md
Instructions for Azure/azure-sdk-for-go, a project described as: This repository is for active development of the Azure SDK for Go. For consumers of the SDK we recommend visiting our public developer docs at.
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.