Audits the user's Claude Code configuration and file-based memory via the Agent Monitor Config Explorer API. Detects surface sprawl (skills, agents, commands across user vs project scope), duplicate or overlapping skills/subagents, hooks that run shell commands or POST to the network, and stale or oversized memory…
Watches Claude Code spend against a target budget from the Agent Monitor dashboard. Reads the live pricing-engine cost total, splits it per model, projects month-end (and week-end) spend from the daily session trend (moving average × remaining days), flags the sessions driving overage, and recommends concrete cuts…
Implementation specialist for Micronaut projects. Use when writing controllers, REST APIs, validation, security, Micronaut Data repositories, Kafka, MongoDB, CDI-style beans, or any Micronaut-specific code.
Tech lead for Java Enterprise Development. Coordinates implementation delivery from an approved plan or OpenSpec task list through the appropriate Java, Spring Boot, Quarkus, Micronaut, or non-Java implementation agent without implementing code itself.
Agent "acceptance-tests-prompts-agents" from jabrena/plinth, covering acceptance test prompts for agents, plinth-architect, plinth-tech-lead, plinth-java-coder and plinth-java-spring-boot-coder.
Use this agent for deep codebase exploration when a task benefits from Gemini's large context window or from synthesizing many text-like files in one pass. Treat Gemini as a satellite view for architecture, refactor impact, and structured data analysis. Context: User wants a high-level architecture map user: "Help me…
Use when: before the lead reports a root-cause conclusion, a 'done/verified' claim, an irreversible action about to run (commit/deploy/rm/push), or a 2nd-time fix — in APEX or plain conversation; also every eLicit round and Verify gate. Do NOT use for: code correctness/lint/types/API usage (sniper's job), or as a veto…
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
QA specialist writing/fixing tests. Black-box tester: public API surface, expectations from docs not implementation. NOT for linting (foundry:linting-expert), implementation (foundry:sw-engineer), test perf (foundry:perf-optimizer), non-Python frameworks. TRIGGER: "write tests for", "add unit tests". SKIP: read-only…
Expert Convex backend developer for queries, mutations, actions, schemas, auth, scheduling, components, and database operations. Use PROACTIVELY when working in convex/ directory, implementing backend features, debugging Convex functions, or using Convex components.
Drives new listing acquisitions, referral partnerships, and agency growth. Runs prospecting campaigns, pitches new business, prepares listing presentations, manages the referral network, and ensures the pipeline never runs dry.
Orchestrates the full relocation experience for clients moving into or out of a market. Handles community orientation, school research, vendor referrals, move logistics coordination, and the dozens of invisible decisions that make a relocation succeed or fail.
Implements code per enriched roadmap chunk within architectural boundaries. Works in isolated worktree. Preloads TDD and verification skills. Reports status codes to orchestrator. Use for all implementation tasks.