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/apache/camel-spring-boot/claude-mdgit clone --depth 1 https://github.com/apache/camel-spring-bootWhat 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.03005 | $0.03005 |
| Opus 5 | $0.01503 | $0.01503 |
| Sonnet 5 | $0.00601 | $0.00601 |
| Haiku 4.5 | $0.00300 | $0.00300 |
Grade A, and why
camel-spring-boot 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 3d 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.
This is a copy
100% identical to camel-spring-boot AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apache Camel Spring Boot - AI Agent Guidelines
Guidelines for AI agents working on this codebase.
Project Info
Apache Camel Spring Boot provides Spring Boot auto-configuration and starter modules for Apache Camel components.
- Version: 4.23.0-SNAPSHOT
- Java: 17+
- Build: Maven (use
./mvnwwrapper) - Issue tracker: JIRA (CAMEL project)
- Related repository: apache/camel — Camel core
AI Agent Rules of Engagement
These rules apply to ALL AI agents working on this codebase.
Attribution
- All AI-generated content (GitHub PR descriptions, review comments, JIRA comments) MUST clearly identify itself as AI-generated and mention the human operator. Example: "Claude Code on behalf of [Human Name]"
PR Volume
- An agent MUST NOT open more than 10 PRs per day per operator to ensure human reviewers can keep up.
- Prioritize quality over quantity — fewer well-tested PRs are better than many shallow ones.
Git branch
- An agent MUST NEVER push commits to a branch it did not create.
- If a contributor's PR needs changes, the agent may suggest changes via review comments, but must not push to their branch without explicit permission.
- An agent should prefer to use his own fork to push branches instead of the main apache/camel-spring-boot repository. It avoids filling the main repository with a long list of uncleaned branches.
- An agent must provide a useful name for the git branch. It should contain the global topic and issue number if possible.
- After a Pull Request is merged or rejected, the branch should be deleted.
JIRA Ticket Ownership
- An agent MUST ONLY pick up Unassigned JIRA tickets.
- If a ticket is already assigned to a human, the agent must not reassign it or work on it.
- Before starting work, the agent must assign the ticket to its operator and transition it to "In Progress".
- Before closing a ticket, always set the correct
fixVersionsfield. Note:fixVersionscannot be set on an already-closed issue — set it before closing, or reopen/set/close if needed.
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.
- 3d ago First seen · 295 lines · 3,005 tokens per session scan A b6a331dc1436
camel-spring-boot CLAUDE.md is an instructions file published in the GitHub repository apache/camel-spring-boot (189 stars, last pushed 4d ago), licensed Apache-2.0. It adds 3,005 tokens to every session, about $0.0150 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to camel-spring-boot AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
camel-spring-boot-examples AGENTS.md
AGENTS.md instructions for apache/camel-spring-boot-examples, covering apache camel spring boot examples - ai agent guidelines, project info, rules of engagement (essentials), repository structure and anatomy of an example.
camel AGENTS.md
AGENTS.md instructions for apache/camel, covering apache camel - ai agent guidelines, project info, ai agent rules of engagement, attribution and pr volume.
camel-quarkus AGENTS.md
Instructions for apache/camel-quarkus, covering apache camel quarkus - ai agent guidelines, project overview, what not to do, technology stack and repository structure.
camel-quarkus-examples AGENTS.md
Instructions for apache/camel-quarkus-examples, covering apache camel quarkus examples - ai agent guidelines, project info, rules of engagement (essentials), repository structure and anatomy of an example.
camel-kamelets AGENTS.md
Instructions for apache/camel-kamelets, covering apache camel kamelets - ai agent guidelines, project info, ai agent rules of engagement, attribution and pr volume.
camel CLAUDE.md
Claude Code instructions for apache/camel, a project described as: Apache Camel is an open source integration framework with 350+ connectors. Write routes in Java, YAML, or XML. Run on Spring Boot, Quarkus, or standalone. Apache License 2.0.