camel-quarkus AGENTS.md

Development guidance for Apache Camel Quarkus, a Java project that connects Apache Camel integration components with the Quarkus application framework. It describes the technology stack, repository layout, and changes to avoid.

In plain words
What is it for?
Use it when changing Camel or Quarkus extensions, running Maven builds, working with native compilation, or navigating the repository.
Why use it?
It helps AI agents work within the project's build system and avoids editing generated files or adding technologies that the project does not use.

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

Made for: Codex, OpenCode.

Per session 3,343 This file is loaded in full into every session.
When invoked 3,343 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.03343 $0.03343
Opus 5 $0.01672 $0.01672
Sonnet 5 $0.00669 $0.00669
Haiku 4.5 $0.00334 $0.00334

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

Security

Grade A, and why

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

AGENTS.md · 291 lines

How it starts

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

Apache Camel Quarkus - AI Agent Guidelines

Rules & guidelines for AI agents working on this codebase.

Project Overview

Apache Camel Quarkus provides Quarkus extensions for Apache Camel components, enabling users to build integration applications with fast boot times and low memory footprints.

What NOT to do

  • Do NOT directly modify generated files under docs/modules or src/main/generated as they are automatically updated by maven
  • Do NOT use dynamic class loading or reflection (impacts native compilation)
  • Do NOT introduce Spring Boot or Spring unless explicitly required
  • Do NOT run ./mvnw process-resources -Pformat -T1C speculatively — it is needed only for certain changes, and only immediately before committing (see "Code Formatting")

Technology Stack

  • Java 17+
  • GraalVM 25+ / Mandrel 25+
  • Maven 3.9.11+ (For convenience the maven wrapper is provided in the root directory and can be invoked as ./mvnw or ./mvnw.cmd)
  • Apache Camel 4.x, Quarkus 3.x. Check pom.xml for the current Camel, and Quarkus versions used.

Repository Structure

extensions/          # Native-supported Camel component extensions
extensions-jvm/      # JVM-only extensions (not yet native-compatible)
extensions-core/     # Core Camel Quarkus extensions (core, yaml-dsl, etc.)
extensions-support/  # Shared support libraries used by multiple extensions
integration-tests/   # Integration tests JVM + native
integration-test-groups/  # Groupings of integration tests, primarilly for boosting CI speed & efficiency
integration-tests-jvm/   # JVM-only extension integration tests
integration-tests-support/ # Shared test utilities and test containers support
poms/bom/            # Runtime Bill of Materials
poms/bom-deployment/ # Deployment Bill of Materials
tooling/             # Maven plugin, scripts, templates, and tooling
catalog/             # Camel Quarkus catalog
docs/                # AsciiDoc documentation (Antora-based)
examples/            # Example projects (separate repo: camel-quarkus-examples)

Read the full file on GitHub · 291 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 · 291 lines · 3,343 tokens per session scan A db9aa8671bd0

Subscribe to this mod's changes

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

Related

Other instructions, from other repositories