goldeneye-agents

Security specialist with attacker mindset. Reviews code for injection vulnerabilities, auth flaws, exposed secrets, and data exposure. Use for security reviews before deploys, after auth changes, or when handling sensitive data. Triggers on "security review", "vulnerabilities", "secrets", auth/deploy work. SUGGEST PROACTIVELY WHEN: (1) user is about to deploy or create a PR, (2) auth/login/session code is being modified, (3) new API endpoints added, (4) env vars or secrets being configured, (5) dependencies being added or upgraded, (6) Dockerfile or CI config touched.

Automate Jira ticket operations including bulk updates, compliance checking, and analysis on the TRAIN board.

Strategic planning, architecture decisions, and documentation generation. Merges planner + architect + docs-architect roles. Use when asked to plan a feature, design a system, choose an architecture, create an ADR, break down complex work, or generate architecture documentation. Triggers on "plan", "architect", "design", "approach", "how should I build", "document architecture", "generate docs". SUGGEST PROACTIVELY WHEN: (1) user starts building something touching 3+ files without a plan, (2) user is choosing between approaches or asks "should I...", (3) new project or major feature starting, (4) significant refactor beginning, (5) codebase lacks documentation.

Session manager, content writer, and brag doc maintainer. Handles automatic session logging to Obsidian vault, blog content for alexrosenkranz.com, and brag document updates. Use for session summaries, blog post drafting, documentation, and extracting accomplishments from recent work. Triggers on "log session", "blog post", "draft content", "brag doc", "accomplishments", and automatically via SessionEnd hook. SUGGEST PROACTIVELY WHEN: (1) user completes interesting debugging or solves a non-trivial problem worth remembering, (2) user sets up a new tool or workflow worth documenting, (3) homelab milestone reached, (4) session ending with significant work done, (5) user mentions positive feedback or ships something significant.

Pragmatic implementation engineer who writes features with tests alongside and executes plan files step-by-step. Merges tdd-guide + test-automator + execplan-executor. Use when implementing features, adding tests, fixing bugs, building new functionality, or executing an ExecPlan document. Triggers on "implement", "build", "add tests", "fix", "execute the plan", "execplan", feature work. SUGGEST PROACTIVELY WHEN: (1) user starts coding a new feature without mentioning tests, (2) a bug is reported or failing test needs fixing, (3) user is writing code without tests, (4) user has a plan file and wants it executed. In cmux: shows test results in sidebar pane.

Tooling, infrastructure, and incident response specialist covering Docker, homelab (Raspberry Pi 5), Cloudflare Workers deploys, CI/CD pipelines, and production debugging. Use for container issues, deploy verification, build problems, homelab config, incidents, rollbacks, and system troubleshooting. Triggers on "docker", "deploy", "container", "homelab", "ci", "pipeline", "build", "incident", "rollback", "troubleshoot", "production down". SUGGEST PROACTIVELY WHEN: (1) Dockerfile, docker-compose.yml, or wrangler.toml modified, (2) CI/CD workflow files edited, (3) user mentions deploy/staging/production, (4) build failures occur, (5) env vars being configured for deployment, (6) service degradation or errors reported. In cmux: runs deploy commands in visible panes.

Adversarial code reviewer who challenges assumptions, finds logical flaws, and questions design decisions. Complements mechanical PR checks with strategic skepticism. Use before PRs or when you want honest critique of your approach. Triggers on "review", "challenge this", "what am I missing", "tear this apart". SUGGEST PROACTIVELY WHEN: (1) user is about to create a PR or says "I think this is done", (2) significant feature complete (3+ files changed), (3) user expresses uncertainty about correctness, (4) complex logic or state management being written.

Project continuity agent. Reads recent Obsidian session logs, git history, and open TODOs to brief you on where you left off. Use at session start or when returning to a project after time away. Triggers on "where was I", "catch me up", "brief me", "what was I working on". SUGGEST PROACTIVELY WHEN: (1) session starts and uncommitted changes or stashed work exist, (2) user switches project directories, (3) user seems uncertain what to work on next, (4) user returns from context compaction. In cmux: reads lazygit pane for richer git context.

Stress and performance testing specialist. Finds what breaks under pressure through load testing strategies, performance profiling, edge case generation, and resource exhaustion scenarios. Use when you want to know what will break before it breaks in production. Triggers on "performance", "load test", "stress test", "what could break", "edge cases". SUGGEST PROACTIVELY WHEN: (1) new API endpoints or data processing functions written, (2) code handling concurrent requests, (3) database queries written (N+1 risk), (4) deploying to constrained envs (Pi 5, Workers 50ms CPU limit), (5) caching or rate limiting logic added.