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/lsampaioweb/ai-instructions/spring-boot-http-clientgit clone --depth 1 https://github.com/lsampaioweb/ai-instructionsWrote 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/lsampaioweb/ai-instructions/spring-boot-http-client)<a href="https://agentmods.dev/instructions/lsampaioweb/ai-instructions/spring-boot-http-client"><img src="https://agentmods.dev/badge/instructions/lsampaioweb/ai-instructions/spring-boot-http-client.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.1 | $0.00471 | $0.00471 |
| Opus 5 | $0.00235 | $0.00235 |
| Sonnet 5 | $0.00094 | $0.00094 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
ai-instructions spring-boot-http-client.instructions.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 yesterday.
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
Spring Boot HTTP Client
Naming Conventions
- Suffix HTTP client classes with
HttpClient. - Suffix HTTP adapter classes with
HttpAdapter. - Suffix HTTP configuration properties classes with
HttpProperties. - Name HTTP client
@Configurationclasses with the*HttpConfigurationsuffix (e.g.,UserHttpConfiguration,PaymentHttpConfiguration).
Rules
- Keep outbound client configuration centralized in a dedicated configuration class.
- Use
RestClient(Spring Framework 6.1+) as the default for imperative HTTP calls. - Use
WebClientonly when reactive streams are required. - Keep endpoint URLs and credentials externalized in properties.
- Bind HTTP client properties using
@ConfigurationPropertiesannotated with@Validated. - Inject
RestClient.Builderinto the*HttpClientclass and construct theRestClientinstance in a@PostConstructmethod using the bound properties. - Use
connectionTimeout=5sandreadTimeout=30sas default timeout values unless the remote API's SLA explicitly requires different values. - Register
.onStatus()handlers on everyRestClientcall chain to map HTTP error responses to domain exceptions before they propagate to the service caller. - Map known remote API error classes to named feature-scoped exceptions in the
.onStatus()handler. - Apply retry logic only for idempotent HTTP methods (GET, PUT, DELETE, HEAD), or for POST/PATCH when the remote API explicitly confirms idempotency.
- Use
ParameterizedTypeReferencefor all generic response types (e.g.,List<T>,PagedModel<EntityModel<T>>) to preserve type information at deserialization. - Use
UriComponentsBuilderfor all dynamic URL construction in outbound calls.
Safety Guards
- Never mix outbound transport concerns into domain models.
- Never disable SSL/TLS certificate verification for outbound HTTP connections.
- Never log outbound request bodies or authorization headers.
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.
- yesterday First seen · 32 lines · 471 tokens per session scan A 185ed77d8817
ai-instructions spring-boot-http-client.instructions.md is an instructions file published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 13d ago), licensed MIT. It adds 471 tokens to every session, about $0.0024 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-09-03.
Other instructions, from other repositories
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.
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.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).