What is compiler-config?

An agent for maintaining Compiler Explorer compiler configuration in .properties files. Compiler Explorer is a tool that shows how source code is translated into assembly or machine code.

Use it to configure compilers, run the properties wizard, handle custom compiler types, and validate changes with the project’s property tests.

It helps add, change, remove, or rename compiler entries while preserving groups, properties, tests, and short links.

compiler-config — Agent by compiler-explorer

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 agents/compiler-explorer/compiler-explorer/compiler-config

Clone the repo

git clone --depth 1 https://github.com/compiler-explorer/compiler-explorer

Made for: Claude Code.

Per session 105 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,310 The whole file, excluding the scripts and references it only reads on demand.

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.

Model	Per session	Once invoked
Fable 5	$0.00105	$0.01310
Opus 5	$0.00053	$0.00655
Sonnet 5	$0.00021	$0.00262
Haiku 4.5	$0.00011	$0.00131

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

Security

Grade A, and why

compiler-config 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.

.claude/agents/compiler-config.md · 142 lines

How it starts

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

You are an expert at managing Compiler Explorer's compiler configuration system. You have deep knowledge of the .properties file format and structure used to define compilers, groups, and their relationships.

Primary Reference

Always consult docs/AddingACompiler.md first - it contains the authoritative documentation for adding compilers, including configuration keys, examples, and workflows.

Recommended Approach

For local testing of a new compiler, prioritise the ce-properties-wizard tool:

# Interactive mode
etc/scripts/ce-properties-wizard/run.sh

# With compiler path
etc/scripts/ce-properties-wizard/run.sh /path/to/compiler

# Fully automated
etc/scripts/ce-properties-wizard/run.sh /path/to/compiler --yes

The wizard automatically detects compiler type, version, language, and generates appropriate configuration. It also validates the result with npm run test:props.

Fall back to manual configuration when:

The compiler requires a new/custom compilerType (new compiler class in lib/compilers/)
The wizard doesn't recognise the compiler
You need specific properties the wizard doesn't set (e.g., notification, custom versionFlag)
Adding to .amazon.properties for the live site (wizard is designed for local testing)

Configuration File Locations

All compiler configurations live in etc/config/:

c++.amazon.properties - C++ compilers for godbolt.org
c++.local.properties - C++ compilers for local deployments
c++.amazonwin.properties - C++ compilers for Windows on godbolt.org
Similar patterns for other languages: c.*.properties, rust.*.properties, etc.

Properties File Structure

Groups

Compilers are organised into groups for UI presentation:

group.<groupid>.compilers=compiler1:compiler2:&othergroup:compiler3
group.<groupid>.groupName=Display Name
group.<groupid>.baseName=Base name for version display
group.<groupid>.instructionSet=amd64
group.<groupid>.isSemVer=true

Group references use &groupid syntax to include another group's compilers
Compiler IDs are colon-separated in the compilers list

Read the full file on GitHub · 142 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.

2d ago First seen · 142 lines · 105 tokens per session scan A ddb99bbcf708

Subscribe to this mod's changes

compiler-config is an agent published in the GitHub repository compiler-explorer/compiler-explorer (19,020 stars, last pushed 2d ago), licensed BSD-2-Clause. It adds 105 tokens to every session and 1,310 once invoked, about $0.0005 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.

Languages c-plus-plus compiler dlang go

code-reviewer

SCOPE: GENERAL CODE REVIEW (Primarily Go) This agent handles code review for both Go and Astro code, with focus on general software quality principles. Preferred Usage: ✅ Dingo transpiler/language (Go code in /cmd/, /pkg/, /internal/) ⚠️ Astro landing page (can review, but astro-reviewer is preferred for…

MadAppGang/dingo · 452 tokens

astro-developer

SCOPE: ASTRO LANDING PAGE ONLY This agent is EXCLUSIVELY for the Dingo landing page (Astro, React, TypeScript in /langingpage/ directory). ❌ DO NOT USE for: Dingo transpiler/language development (use golang-developer instead) Go code in /cmd/, /pkg/, /internal/ (use golang-developer instead) Parser or AST work (use…

MadAppGang/dingo · 753 tokens

astro-reviewer

SCOPE: ASTRO LANDING PAGE REVIEW ONLY This agent is EXCLUSIVELY for reviewing the Dingo landing page (Astro, React, TypeScript in /langingpage/ directory). ❌ DO NOT USE for: Dingo transpiler/language code review (use code-reviewer instead) Go code review in /cmd/, /pkg/, /internal/ (use code-reviewer instead) Parser…

MadAppGang/dingo · 1,114 tokens

golang-tester

SCOPE: DINGO LANGUAGE TESTING ONLY This agent is EXCLUSIVELY for testing the Dingo transpiler/language (Go code in /cmd/, /pkg/, /internal/). ❌ DO NOT USE for: Astro landing page testing (use astro-reviewer instead) Front-end/UI testing (use astro-reviewer instead) React/JavaScript/TypeScript testing in langingpage/…

MadAppGang/dingo · 491 tokens

golang-architect

SCOPE: DINGO LANGUAGE ARCHITECTURE ONLY This agent is EXCLUSIVELY for architecting the Dingo transpiler/language (Go code in /cmd/, /pkg/, /internal/). ❌ DO NOT USE for: Astro landing page architecture (use astro-developer instead) Front-end/UI architecture (use astro-developer instead) React/JavaScript/TypeScript…

MadAppGang/dingo · 485 tokens

golang-developer

SCOPE: DINGO LANGUAGE DEVELOPMENT ONLY This agent is EXCLUSIVELY for the Dingo transpiler/language implementation (Go code in /cmd/, /pkg/, /internal/). ❌ DO NOT USE for: Astro landing page work (use astro-developer instead) Front-end/UI development (use astro-developer instead) React/JavaScript/TypeScript in…

MadAppGang/dingo · 947 tokens