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/kaotoio/forage/claude-mdgit clone --depth 1 https://github.com/KaotoIO/forageWrote 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/kaotoio/forage/claude-md)<a href="https://agentmods.dev/instructions/kaotoio/forage/claude-md"><img src="https://agentmods.dev/badge/instructions/kaotoio/forage/claude-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.03075 | $0.03075 |
| Opus 5 | $0.01537 | $0.01537 |
| Sonnet 5 | $0.00615 | $0.00615 |
| Haiku 4.5 | $0.00308 | $0.00308 |
Grade A, and why
forage CLAUDE.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 5d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
Forage is a plugin extension for Apache Camel that provides opinionated bean factories for simplified component configuration. The library eliminates manual Java bean instantiation by providing factory classes configurable through properties files, environment variables, or system properties.
Technology Stack:
- Java 17+
- Apache Camel 4.x
- LangChain4j 1.x
- Maven, Spotless (Palantir Java Format), JUnit 5, AssertJ, Testcontainers, Citrus Test Framework
Branching and Versioning Strategy
Forage uses major.minor.micro versioning (1.4.0, 1.4.1, 1.6.0, etc.), tracked
micro-to-micro against Apache Camel on the current-LTS line (1.6.0 ↔ Camel 4.22.0,
1.6.1 ↔ Camel 4.22.1, etc.).
| Branch | Tracks | Version | Status |
|---|---|---|---|
main |
Current Camel LTS | 1.6.x |
Follows the current Camel LTS release (currently 4.22.x). Active, primary branch — micro bumps (1.6.0 → 1.6.1 → ...) for each release. |
camel-4.18.x |
Previous Camel LTS | 1.4.x |
Maintenance branch for the previous LTS line (Camel 4.18.x), branched from main when Camel 4.22 became LTS. Micro bumps (1.4.1 → 1.4.2 → ...) as needed. |
camel-latest |
Latest (non-LTS) Camel | 1.5.x |
Dormant. Frozen at Camel 4.20.x / Forage 1.5.x until Apache Camel ships its next post-LTS "latest" release (expected around 4.23), at which point it's rebased from main and resumes releases. |
When a new Camel LTS lands, the current main line becomes the new camel-N.M.x
maintenance branch (via a fresh branch off main, not a rename), main is upgraded
in place to track the new LTS, and camel-latest is re-evaluated against whatever
Camel considers "latest" at that point.
Backporting
When making changes (features, bug fixes, etc.), always investigate whether the change needs backporting to the other active branch(es):
- A fix on
mainmay also apply tocamel-4.18.x(and tocamel-latestonce it's active again), and vice versa. - After completing work on one branch, check if the same change is relevant to the other branch(es) and create a backport PR if needed.
- Use
/oss-backport-prto automate backporting when applicable.
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.
- 5d ago First seen · 266 lines · 3,075 tokens per session scan A da556443ac21
forage CLAUDE.md is an instructions file published in the GitHub repository KaotoIO/forage (22 stars, last pushed 7d ago), licensed Apache-2.0. It adds 3,075 tokens to every session, about $0.0154 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
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.
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.