Agent Profile

agent-profile

Portable agent runtime profile for Codex CLI and Claude Code.

This repo owns one public, shareable instruction file and a small marketplace of installable plugins. It replaces ad hoc dotfile sync for agent instructions and skills without taking ownership of private local overrides.

What This Owns

• AGENTS.md is the canonical shared user-level instruction file.
• ~/.codex/AGENTS.md should be a symlink to AGENTS.md.
• ~/.claude/CLAUDE.md should be a symlink to AGENTS.md.
• plugins/engineering-practices contains language, tooling, and quality skills.
• plugins/agent-workflows contains reusable workflow skills.

Private notes do not belong in this repo. Use `~/.codex/AGENTS.override.md`, `~/.claude/CLAUDE.local.md`, or another local-only file outside this repository.

Install

Clone the profile repo from GitHub:

git clone https://github.com/alleneubank/agent-profile.git ~/.agent-profile
cd ~/.agent-profile

Check current runtime state:

./install.sh --check

Apply safe fixes:

./install.sh --fix

If an instruction target is a real file instead of a symlink, the installer refuses to replace it. To back it up and replace it with the repo symlink:

./install.sh --fix --replace-existing

direnv in agent tool calls

Agents run each tool call in a fresh, non-interactive shell. direnv's normal hook is prompt-driven, so it never fires there and an allowed `.envrc` silently does not reach the agent — the symptom is a token or a `PATH` entry that is present in your terminal and absent in the agent's.

This is a shell-configuration problem, not something a plugin should solve. A hook that rewrites the command to load direnv works, but the rewritten command then contains `$(...)`, which Claude Code and Codex cannot statically analyse, so every `Bash(...)` allow rule stops matching and each call needs approval. Fix the shell instead; the environment then arrives before the tool call is even m