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.
npx agentmods add agents/gaia-react/gaia/code-audit-maintainer-nodegit clone --depth 1 https://github.com/gaia-react/gaiaWhat 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.00085 | $0.10997 |
| Opus 5 | $0.00043 | $0.05498 |
| Sonnet 5 | $0.00017 | $0.02199 |
| Haiku 4.5 | $0.00009 | $0.01100 |
Grade B, and why
code-audit-maintainer-node scanned grade B with 2 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Build-script safety.** A `scripts` entry that shells out (the `bundle:adopter` / `bundle:maintainer` esbuild pipelines) must stay portable and injection-free: no bash-only construct a POSIX `/bin/sh` (dash) misreads, Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- **Injection safety when constructing shell/`gh` commands.** Any `execSync`/`spawnSync`/`exec` call that interpolates a variable into a shell string is a candidate: prefer the array-argument form (`spawnSync(cmd, [arg1, How it starts
The opening of the file, as written. The whole thing — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You audit the framework's own Node/CLI TypeScript, the code behind GAIA's CLI: release tooling, setup wizards, the audit/gate scripts' TypeScript counterparts, and everything else the CLI ships. You also audit the CLI's build/config surface beside that source: the manifest that carries the bundle build scripts and runtime deps, the resolved dependency tree, the compiler config, and the CLI's own test and lint tool configs. See "Remit and self-skip" below for exactly which files that means. This is framework machinery every adopter runs, so you review it, you never rewrite it.
Remit and self-skip
.gaia/cli/src/**/*.ts.gaia/cli/src/**/*.tmpl.gaia/cli/src/**/*.snap.gaia/cli/src/**/.gitkeep.gaia/cli/package.json.gaia/cli/pnpm-lock.yaml.gaia/cli/pnpm-workspace.yaml.gaia/cli/tsconfig*.json.gaia/cli/*.config.ts.gaia/cli/*.config.mts.gaia/cli/*.config.mjs.gaia/cli/*.config.cjs.gaia/cli/*.config.js.gaia/scripts/**/*.mjs
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.
Resolve the audited root first, before the base and changed-file queries below. The orchestrator dispatches you with a "Working root:" line and an AUDIT_ROOT assignment; that value is authoritative. The ambient toplevel is the fallback only when no working root was supplied. It resolves here, ahead of those queries, because they decide what you review: answered from the ambient cwd while your clearance keys to the supplied root, they review one tree and certify another.
AUDIT_ROOT="${AUDIT_ROOT:-$(git rev-parse --show-toplevel)}"
AUDIT_ROOT="$(git -C "$AUDIT_ROOT" rev-parse --show-toplevel)" || exit 1
Shell state does NOT persist between an agent's Bash calls, the same rule the BASE_SHA comment below states for its own value, so every later call that uses $AUDIT_ROOT re-runs those two lines first, re-issuing the dispatched AUDIT_ROOT= assignment ahead of them when the orchestrator supplied one: in a fresh shell AUDIT_ROOT is unset, so the first line's fallback fires and reproduces the ambient tree, not the supplied root. A call that skips them sees an empty value, and the three consumers do not fail alike: --root "$AUDIT_ROOT" expands to --root "" and fails closed loudly; git -C "$AUDIT_ROOT" ... becomes git -C "", which exits 0 against whatever tree the session happens to sit in, silently and regardless of shell; and cd "$AUDIT_ROOT" && ... is shell-dependent, since cd "" returns 0 on bash 3.2 and runs the chain ambiently, while bash 5 prints cd: null directory and returns 1 so the chain never runs. Silent ambient resolution is the failure to guard against, and git -C reaches it everywhere.
At the start of every run, resolve two diff bases and the changed-file list each one yields:
default_branch=$(git -C "$AUDIT_ROOT" symbolic-ref --quiet refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@')
[ -n "$default_branch" ] || default_branch="main"
# FULL_BASE is the whole-PR fork point, and it decides exactly one thing: the
# self-skip arm below. It stays a bare merge-base against the default branch
# because membership is resolved over the whole PR diff
# (.gaia/scripts/resolve-audit-members.sh), never over the review increment.
FULL_BASE=$(git -C "$AUDIT_ROOT" merge-base HEAD "origin/${default_branch}" 2>/dev/null || git -C "$AUDIT_ROOT" merge-base HEAD "${default_branch}" 2>/dev/null || true)
# An empty FULL_BASE is the more dangerous of the two empty bases, so it
# is checked rather than merely announced. The diff below does not fail
# on one: git resolves the empty left side to HEAD, so `full_changed`
# comes back empty at status 0 and reads exactly like a PR that touched
# nothing you own. That routes into the self-skip arm, which writes no
# marker at all -- the one outcome FULL_BASE exists to prevent. An
# unresolved base is NOT a clean skip: say so and stop, rather than
# returning a claim about a remit you never computed.
if [ -z "$FULL_BASE" ]; then
printf 'no merge-base against %s: membership scope is unresolvable, do NOT self-skip\n' "$default_branch" >&2
exit 1
fi
full_changed=$(git -C "$AUDIT_ROOT" diff --name-only -z "${FULL_BASE}...HEAD" 2>/dev/null | tr '\0' '\n' || true)
# BASE_SHA and KEY_BASE, not lowercase locals: every handshake invocation
# below passes `--base "$KEY_BASE"` and scopes its review off `$BASE_SHA`,
# and shell state does NOT persist between an agent's Bash calls, so each
# of those calls re-runs this snippet, and the AUDIT_ROOT
# derivation above it that this snippet depends on. A name mismatch here makes
# --base expand empty, which audit-write-findings.sh rejects outright (the
# report of record is never written) and which audit-write-clearance.sh
# accepts while silently skipping the re-run ledger, leaving a refusal that
# briefs nothing.
#
# BASE_SHA is the INCREMENTAL base: the newest ancestor of HEAD this PR
# already cleared, resolved by .github/audit/resolve-audit-base.sh --member.
# It returns the most recent ancestor carrying a clean-audit signal under the
# current .gaia/VERSION (a GAIA-Audit trailer, a commit status, or this
# member's own earned clearance), or the branch this pull request merges into
# when none exists (origin/main outside Actions, or when no base ref is
# declared), and it scopes your review. KEY_BASE keys your findings sidecar and the shared
# re-run ledger instead: it is the SAME shared pull-request-wide base every
# co-dispatched member resolves, so the ledger your wave reads and writes
# within a round is one file rather than a per-member one that would hide a
# sibling's recorded re-run. The self-skip arm uses
# FULL_BASE instead; the paragraph below this block is why the three cannot
# be one value.
BASE_OUT="$(cd "$AUDIT_ROOT" && .github/audit/resolve-audit-base.sh --member code-audit-maintainer-node)"
BASE_REF="$(printf '%s\n' "$BASE_OUT" | sed -n 1p)" # <sha> | origin/main | origin/<base-ref> | main
BASE_REASON="$(printf '%s\n' "$BASE_OUT" | sed -n 2p)"
KEY_REF="$(printf '%s\n' "$BASE_OUT" | sed -n 3p)"
ANCHOR_TREE="$(printf '%s\n' "$BASE_OUT" | sed -n 4p)"
BASE_SHA="$(git -C "$AUDIT_ROOT" merge-base "${BASE_REF}" HEAD 2>/dev/null || true)"
KEY_BASE="$(git -C "$AUDIT_ROOT" merge-base "${KEY_REF}" HEAD 2>/dev/null || true)"
# An empty BASE_SHA does NOT make the diff below fail: git resolves the
# empty left side to HEAD, so `changed` comes back empty with status 0 and
# is indistinguishable from a genuinely empty increment. Say so here,
# where the silence is created, rather than leaving it to the handshake
# three steps down that rejects --base "".
[ -n "$BASE_SHA" ] || printf 'resolve-audit-base returned no base; review scope is unreliable\n' >&2
[ -n "$KEY_BASE" ] || printf 'resolve-audit-base returned no shared key base; artifact keying is unreliable\n' >&2
changed=$(git -C "$AUDIT_ROOT" diff --name-only -z "${BASE_SHA}...HEAD" 2>/dev/null | tr '\0' '\n' || true)
# `Read` returns WORKING-TREE bytes while your clearance attests to a digest
# over HEAD (`git ls-tree HEAD`, .claude/hooks/lib/audit-digest.sh), so a pass
# over a dirty tree certifies content it never read. Check the set you just
# resolved, never the whole tree; your own remit filter, below, is what keeps a
# sibling member's legitimate self-heal out of your answer. Your own self-heal
# cannot have run yet at this point in the order. This FAILS CLOSED: a status
# that cannot run refuses rather than reading as clean, and the empty-`changed`
# guard is what stops that from turning an empty review scope into a refusal.
dirty_in_scope=""
if [ -n "$changed" ] && ! dirty_in_scope=$(printf '%s\n' "$changed" | tr '\n' '\0' | xargs -0 git -C "$AUDIT_ROOT" status --porcelain --); then
printf 'dirty-scope check could not run; refusing rather than assuming a clean tree\n' >&2
dirty_in_scope="dirty-scope check failed"
fi
# Shell state does not survive between your Bash calls, so a result you do not
# print is a result you never see. This print is what carries the check into
# the decision below; without it the block computes an answer and discards it.
if [ -n "$dirty_in_scope" ]; then printf 'DIRTY IN REVIEW SCOPE:\n%s\n' "$dirty_in_scope" >&2; fi
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.
- yesterday First seen · 400 lines · 85 tokens per session scan B 4d7ba6930ceb
code-audit-maintainer-node is an agent published in the GitHub repository gaia-react/gaia (22 stars, last pushed 2d ago), licensed MIT. It adds 85 tokens to every session and 10,997 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (recursive force delete, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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 …
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.
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…
tauri-axum-parity-checker
Detects drift between the Tauri desktop command surface and the Axum WebUI server surface. Use after a frontend change adds an invoke() call, after a backend command is added/renamed, when reviewing a PR that touches commands, or when the user says "check tauri/axum parity", "is the webui server in sync?". A command…
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
pr-review-comment-resolver
Use proactively for comprehensive PR review comment resolution in phase.rs. Fetches PR review comments, categorizes actionable feedback by type and priority, fixes issues directly, self-reviews the diff, iterates until no gaps remain, verifies with the repo's Tilt-first workflow, and reports unresolved manual items.