camel-kamelets AGENTS.md

Project instructions for the Apache Camel Kamelet Catalog, a collection of reusable YAML route templates for moving and processing data with Apache Camel. They describe the project, build commands, agent rules, attribution requirements, and limits on opening pull requests.

In plain words
What is it for?
Use them when editing Kamelets, running Maven verification or generators, checking Java and Go requirements, or preparing AI-generated pull-request and issue content.
Why use it?
They give coding agents the project context and contribution rules needed to make changes that fit the catalog and its review process.

Instructions file for CodexOpenCode

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-kamelets/agents-md
Clone the repo
git clone --depth 1 https://github.com/apache/camel-kamelets

Made for: Codex, OpenCode.

Per session 3,698 This file is loaded in full into every session.
When invoked 3,698 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.03698 $0.03698
Opus 5 $0.01849 $0.01849
Sonnet 5 $0.00740 $0.00740
Haiku 4.5 $0.00370 $0.00370

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

Security

Grade A, and why

camel-kamelets 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 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.

AGENTS.md · 331 lines

How it starts

The opening of the file, as written. The whole thing — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Apache Camel Kamelets - AI Agent Guidelines

Guidelines for AI agents working on this codebase.

Project Info

The Apache Camel Kamelet Catalog is the default catalog of reusable Camel route templates ("Kamelets"), distributed as Kubernetes-style YAML and consumed by Camel, Camel K, Camel Quarkus and Camel Spring Boot.

  • Version: 4.20.0
  • Camel: 4.20.0
  • Java: 17+
  • Build: Maven (mvn verify); Go is required for the script/ and crds/ generators
  • Issue tracker: GitHub — https://github.com/apache/camel-kamelets/issues
  • Related repository: apache/camel (Camel core — the Kamelet runtime lives there, not here)

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, issue 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 its own fork to push branches instead of the main apache/camel-kamelets repository, to avoid filling the main repository with uncleaned branches.
  • Branch names: fix-issue → ci-issue-<ISSUE_NUMBER>, quick-fix → quick-fix/<short-slug>, CI fix → ci-fix/<short-slug>. Include the topic and issue number where possible.
  • After a Pull Request is merged or rejected, delete the branch.

GitHub Issue Ownership

  • An agent MUST ONLY pick up unassigned GitHub issues.
  • If an issue is already assigned to a human, the agent must not reassign it or work on it.
  • Before starting work, assign the issue to its operator.
  • Beginner tasks carry the good first issue label; experienced tasks carry help wanted.

Read the full file on GitHub · 331 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. yesterday First seen · 331 lines · 3,698 tokens per session scan A d72181c4aaf9

Subscribe to this mod's changes

camel-kamelets AGENTS.md is an instructions file published in the GitHub repository apache/camel-kamelets (71 stars, last pushed 2d ago), licensed Apache-2.0. It adds 3,698 tokens to every session, about $0.0185 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.