camel-quarkus-examples AGENTS.md

Project instructions for AI agents contributing to Apache Camel Quarkus examples, which are sample applications showing Apache Camel running with Quarkus. They describe the tools, project structure, testing approach, issue tracker, and contribution rules.

In plain words
What is it for?
Working on Camel Quarkus example applications, including running Maven builds, using the required Java versions and tests, managing dependencies, and preparing properly attributed contributions.
Why use it?
They give an agent the repository-specific context needed to make changes that follow the project's build, testing, dependency, and review conventions.

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

Made for: Codex, OpenCode.

Per session 1,441 This file is loaded in full into every session.
When invoked 1,441 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.01441 $0.01441
Opus 5 $0.00720 $0.00720
Sonnet 5 $0.00288 $0.00288
Haiku 4.5 $0.00144 $0.00144

Measured 2d ago against content hash fe38c1452f5f, 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-examples 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 · 125 lines

How it starts

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

Apache Camel Quarkus Examples - AI Agent Guidelines

Guidelines for AI agents contributing examples to apache/camel-quarkus-examples.

This repository contains runnable example applications that demonstrate Apache Camel running on Quarkus, in JVM and native mode.

For the canonical, project-wide agent rules, see the Camel Quarkus AGENTS.md. The notes below adapt the essentials to this examples repository — note that Camel Quarkus follows GitHub-based conventions that differ from Apache Camel core (e.g. GitHub issues instead of JIRA).

Project Info

  • Build: Maven 3.9+ (use the provided ./mvnw wrapper)
  • Java: 17+ (CI also exercises JDK 21)
  • BOMs: quarkus-bom + quarkus-camel-bom (extension versions are inherited, never pinned per-dependency)
  • Tests: @QuarkusTest (JVM) and @QuarkusIntegrationTest (packaged/native)
  • Issue tracker: GitHub issues at https://github.com/apache/camel-quarkus/issues (Camel Quarkus does not use JIRA)

Rules of Engagement (essentials)

  • Attribution: every AI-generated PR description, review or issue comment MUST identify itself as AI-generated and name the human operator, e.g. _Claude Code on behalf of [Human Name]_.
  • Target the camel-quarkus-main branch for PRs (it tracks the current Camel Quarkus SNAPSHOT), as stated in the repository's PR template. The main branch tracks the latest released Quarkus Platform.
  • One example per PR, kept small and self-contained. Do not exceed 10 PRs per day per operator. Quality over quantity.
  • Branch from your own fork (not apache/), with a descriptive name (include the GitHub issue number when there is one, e.g. 123-rest-json-example). Delete the branch after merge/close. Never push to a branch you did not create.
  • Green CI is required, including license/format/import checks and (where applicable) the native build.
  • Never merge without at least one human approval; never approve your own PR.

Read the full file on GitHub · 125 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 · 125 lines · 1,441 tokens per session scan A fe38c1452f5f

Subscribe to this mod's changes

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