agentmods.dev

camel-spring-boot AGENTS.md

A set of working rules for AI agents contributing to Apache Camel Spring Boot, a Java project that configures Apache Camel components for Spring Boot applications. It describes the project, build commands, attribution requirements, and limits on pull requests and branch use.

In plain words
What is it for?
Use it when modifying or reviewing this project, preparing pull requests or issue comments, building with Maven, and deciding which branch an agent may push to.
Why use it?
It helps agents follow the repository's contribution rules and avoid unsafe changes to other contributors' branches. It also makes AI-generated contributions identifiable.

Instructions file for CodexOpenCode

189 2d ago A scan 3,005 tokens original Apache-2.0
View the source file apache/camel-spring-boot
Install

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.

agentmods
npx agentmods add instructions/apache/camel-spring-boot/agents-md
Clone the repo
git clone --depth 1 https://github.com/apache/camel-spring-boot

Made for: Codex, OpenCode.

Per session 3,005 This file is loaded in full into every session.
When invoked 3,005 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash b6a331dc1436, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

camel-spring-boot 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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 295 lines

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.

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 fixVersions field. Note: fixVersions cannot be set on an already-closed issue — set it before closing, or reopen/set/close if needed.

Read the full file on GitHub · 295 lines

Changes

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.

  1. 2d ago First seen · 295 lines · 3,005 tokens per session scan A b6a331dc1436

Subscribe to this mod's changes

camel-spring-boot AGENTS.md is an instructions file published in the GitHub repository apache/camel-spring-boot (189 stars, last pushed 2d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflowLanguagesPlanningcamelcloud-nativeintegrationjavamicroservicesspring-boot
Related

Other instructions, from other repositories

camel AGENTS.md

Instructions for apache/camel, covering apache camel - ai agent guidelines, project info, ai agent rules of engagement, attribution and pr volume.

apache/camel · 7,481 tokens

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.

apache/camel-spring-boot-examples · 1,351 tokens

camel CLAUDE.md

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.

apache/camel · 3 tokens

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.

apache/camel-quarkus · 3,343 tokens

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.

apache/camel-quarkus-examples · 1,441 tokens

camel-quarkus CLAUDE.md

Instructions for apache/camel-quarkus, a project described as: Apache Camel Quarkus.

apache/camel-quarkus · 3 tokens