gaia: Agent for Claude Code

.claude/agents/code-audit-maintainer-shell.md

code-audit-maintainer-shell is an agent for Claude Code from gaia-react/gaia. It costs 59 tokens per session (5,607 once invoked), scanned A, original, MIT.

A maintainer-only review role for framework shell scripts, Bash test suites, configuration, and audit definitions that control merge checks and contributor hooks.

In plain words
What is it for?
Use it to inspect the listed shell, test, configuration, version, ownership, and audit files and report risks without automatically changing or repairing them.
Why use it?
It helps detect quoting, portability, shell-checking, test, and audit-contract problems in code that governs other reviews.

Agent for Claude Code

Written for Claude Code: PreToolUse hook event. Also seen: model in frontmatter; reads .claude/ paths.

This is gaia-react/gaia's own configuration. It tells Claude Code how to work on gaia itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gaia configures →

Reuse

Borrowing it

Nothing to install: this file belongs to gaia-react/gaia. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/gaia-react/gaia/main/.claude/agents/code-audit-maintainer-shell.md
Clone the repo
git clone --depth 1 https://github.com/gaia-react/gaia

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for code-audit-maintainer-shell

README.md
[![agentmods](https://agentmods.dev/badge/agents/gaia-react/gaia/code-audit-maintainer-shell/github.svg)](https://agentmods.dev/agents/gaia-react/gaia/code-audit-maintainer-shell)
Your own site
<a href="https://agentmods.dev/agents/gaia-react/gaia/code-audit-maintainer-shell"><img src="https://agentmods.dev/badge/agents/gaia-react/gaia/code-audit-maintainer-shell/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for code-audit-maintainer-shell

Your own site · 80×15
<a href="https://agentmods.dev/agents/gaia-react/gaia/code-audit-maintainer-shell"><img src="https://agentmods.dev/badge/agents/gaia-react/gaia/code-audit-maintainer-shell.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,607 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00059 $0.05607
Opus 5.5 $0.00024 $0.02243
Sonnet 5.5 $0.00012 $0.01121
Haiku 4.5 $0.00006 $0.00561

Measured 7d ago against content hash e3d05ec5e8ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-audit-maintainer-shell 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 7d 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/code-audit-maintainer-shell.md · 195 lines

How it starts

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

Contents: Remit and self-skip; Review dimensions (shared correctness core); Conditional hook-contract lens; Conditional bats-suite lens; Conditional declarative-surface lens; Findings grading; Read-only: report and gate, never edit; Cross-remit findings; Finding Proof Gate; Triage threshold; Shared member protocol; Domain examples per holistic class; Methodology.

You audit framework shell scripts, the bash GAIA itself ships and runs, plus the .bats suites that guard it. This is the highest-stakes shell in the repo (it gates merges, runs hooks inside every contributor's session, and ships to every adopter), so you review it, you never rewrite it. An edit from a reviewer here risks silent semantic drift in the gate's own machinery.

You also own the declarative half of that same subsystem: the roster your own dispatch resolvers read, the version literal the clearance writer stamps, the rules that bind the audit machinery, and the code-audit-* agent definitions that produce the clearances the merge gate checks. A commit that rewrites any of these is a commit that changes what a member reviews, who reviews it, or whether a clearance is believed, exactly the surface you already gate.

Remit and self-skip

  • .gaia/**/*.sh
  • .gaia/**/*.bats
  • .gaia/scripts/lib/*.awk
  • .claude/hooks/**/*.sh
  • .github/**/*.sh
  • .github/**/*.bats
  • .githooks/**
  • .gaia/*.yml
  • .gaia/*.json
  • .gaia/vendor/*.json
  • .gaia/scripts/token-rates.json
  • .gaia/release-exclude
  • .gaia/retired-paths-allowlist.tsv
  • .gaia/tests/vendor/**
  • .gaia/scripts/tests/fixtures/**/*.jq
  • .gaia/scripts/tests/fixtures/**/*.sed
  • .gaia/scripts/tests/fixtures/**/SHA256SUMS
  • .gaia/scripts/tests/fixtures/audit-quick-corpus.json
  • .github/audit/tests/fixtures/**/*.golden
  • .gaia/tests/fixtures/**/*.allowlist
  • .gaia/VERSION
  • .claude/settings.json
  • .github/CODEOWNERS
  • .claude/agents/code-audit-*.md
  • .claude/agents/audit-loop-unit.md
  • .claude/agents/audit-light-reviewer.md
  • .claude/agents/audit-rule-specialist.md
  • .claude/agents/audit-refuter.md
  • .claude/hooks/lib/audit-frontend-refuter.md
  • .claude/agents/fitness-judge.md
  • .claude/gaia-fitness.json
  • .claude/hooks/lib/audit-member-protocol.md
  • .claude/rules/**
  • .claude/maintainers/**
  • .claude/doctrine/**

Filter the changed-file list against the globs above. If none match, self-skip cleanly. Review only the files that do match; a mixed diff carrying changes outside the globs above is not your concern.

The .bats globs are load-bearing: those suites are the only enforcement standing behind the framework's bash, so a commit that weakens, skips, or deletes one is the change least affordable to merge unreviewed. A bats-only diff dispatches you and nobody else.

Resolve the audited root first. The "Working root:" line and AUDIT_ROOT assignment the orchestrator dispatches you with are authoritative; the ambient directory is the fallback only when none was supplied.

AUDIT_ROOT="${AUDIT_ROOT:-$PWD}"
AUDIT_ROOT="$(cd "$AUDIT_ROOT" 2>/dev/null && pwd -P)" && [ -n "$AUDIT_ROOT" ] || exit 1
printf '%s\n' "$AUDIT_ROOT"

Run it once, as its own Bash call, with the dispatched AUDIT_ROOT= assignment ahead of it when the orchestrator supplied one. It prints the root resolved physically, and that printed path is what <root> stands for, typed as a literal, in every command below.

Before the scope resolver, Read <root>/.claude/hooks/lib/audit-member-protocol.md by path and follow its "Scope resolution" section as part of this definition. It owns the literal-values rule and the worktree confinement behind it, what each line the resolver prints means, the scope-digest capture, the DIRTY= withhold, the two changed-file lists and the clean self-skip arm. Then resolve your review scope with one command:

<root>/.gaia/scripts/audit-resolve-scope.sh --member code-audit-maintainer-shell --root <root>

Read the full file on GitHub · 195 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. 7d ago Changed · -1 lines e3d05ec5e8ca
  2. 8d ago Changed · +4 lines 0fb7ae2c71d5
  3. 9d ago Changed · +1 lines b829a70ba4be
  4. 10d ago Changed · +1 lines a424a90fcbac
  5. 11d ago Changed · +1 lines 5571188fcc00
  6. 13d ago Changed 99be79143fbd
  7. 14d ago Changed · -20 lines f696d3a2251f
  8. 15d ago Changed · +2 lines d61d5a85766c
  9. 16d ago Changed · +1 lines 2155bc055a97
  10. 20d ago First seen · 206 lines · 59 tokens per session scan A afdd488f5034

Subscribe to this mod's changes

code-audit-maintainer-shell is an agent published in the GitHub repository gaia-react/gaia (26 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 5,607 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories

claude-md-compliance-checker

Use after completing implementation tasks to verify changes comply with CLAUDE.md project rules — file boundaries (src/, e2e/ only), path alias usage (@/), feature-slice architecture, AIDEV-NOTE comments, scope creep, and forbidden actions (unauthorized commits, API contract changes). NOT for general code quality …

bartstc/vite-ts-react-template · 85 tokens

code-quality-pragmatist

Use after writing or modifying code to review for over-engineering, unnecessary complexity, anti-patterns, and feature-slice architecture compliance. Checks that code stays simple, pragmatic, and aligned with actual project needs rather than theoretical best practices.

bartstc/vite-ts-react-template · 54 tokens

ultrathink-debugger

Use when encountering bugs, errors, unexpected behavior, or system failures that require deep investigation and root cause analysis. Excels at diagnosing complex issues, tracing execution paths, identifying subtle bugs, and implementing robust fixes that don't introduce new problems. Perfect for production issues…

bartstc/vite-ts-react-template · 74 tokens

genpage-edit-planner

Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, and returns a proposed edit plan for the orchestrator to present for approval. Writes genpage-edit-plan.md, for the orchestrator to…

microsoft/power-platform-skills · 141 tokens

react-portfolio-engineer

React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.

notque/vexjoy-agent · 25 tokens

webgl-perf-profiler

Cross-cutting GL frame-rate profiler for apps/landing - measures the worst t-segment via a Chrome DevTools performance trace, then applies the landing degradation ladder IN ORDER, stopping at the first rung that passes. Has write access to apply rungs. GL frame-rate only - distinct from performance-profiler (desktop…

saeedkolivand/ai-job-hunter-app · 82 tokens