786 boosters for "Agent" — open source, verified from GitHub, ready to install
Review the most recent commit (or the commit specified in ) in a single pass, using FXA-specific knowledge. Use Read and Grep to examine the changed files and their surrounding context. Look at imports, callers, and related types to understand the full picture before judging. Evaluate the diff throu
Use this agent when documentation in the `architecture/` directory needs to be updated or created for a specific file after implementing a feature, fix, refactor, or behavior change. Launch one instance of this agent per file that needs updating. This agent maintains the *contents* of architecture documentation files — it does not decide which files exist or how the directory is organized.\n\nExamples:\n\n- Example 1:\n Context: A developer just finished implementing OPA policy evaluation in the sandbox system.\n user: "I just finished implementing the OPA engine in crates/openshell-sandbox/src/opa.rs. Update architecture/sandbox.md to reflect the new policy evaluation flow."\n assistant: "I'll launch the arch-doc-writer agent to update the sandbox architecture documentation with the new OPA policy evaluation details."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/sandbox.md>\n\n- Example 2:\n Context: A refactor changed how the HTTP CONNECT proxy handles allowlists.\n user: "The proxy allowlist logic was refactored. Please update architecture/proxy.md."\n assistant: "Let me use the arch-doc-writer agent to synchronize the proxy documentation with the refactored allowlist logic."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/proxy.md>\n\n- Example 3:\n Context: After implementing a new CLI command, the assistant proactively updates docs.\n user: "Add a --rego-policy flag to the CLI."\n assistant: "Here is the implementation of the --rego-policy flag."\n <implementation complete>\n assistant: "Now let me launch the arch-doc-writer agent to update the CLI architecture documentation with the new flag."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/cli.md>\n\n- Example 4:\n Context: A user wants high-level overview documentation for a non-engineering audience.\n user: "Update architecture/overview.md with a non-engineer-friendly explanation of the sandbox system."\n assistant: "I'll launch the arch-doc-writer agent to create an accessible overview of the sandbox system for non-technical readers."\n <uses Task tool to launch arch-doc-writer with audience=non-engineer directive>\n\n- Example 5:\n Context: Multiple files need updating after a large feature lands.\n user: "I just landed the network namespace isolation feature. Update architecture/sandbox.md and architecture/networking.md."\n assistant: "I'll launch two arch-doc-writer agents — one for each file — to update the documentation in parallel."\n <uses Task tool to launch arch-doc-writer for architecture/sandbox.md>\n <uses Task tool to launch arch-doc-writer for architecture/networking.md>
Use this agent to review existing code, audit plans, evaluate product requirements, or get architectural guidance that balances pragmatism, user experience, and security. This includes code reviews, plan audits, architecture reviews, security assessments, or when building engineering and development plans from requirements. Use proactively after significant code changes or before merging.
"name": "antigravity-skills", "description": "Professional Agent Skills collection for full-stack development, logic planning, and multimedia processing.", "email": "guanyangsunlight@gmail.com",
Browse once, cache the APIs, reuse them instantly. First call discovers and learns the site's APIs (~20-80s). Every subsequent call uses cached skills (<200ms for server-fetch, ~2s for sites requiring browser execution). When the task touches docs, install guidance, eval claims, landing-page copy, r
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json", "name": "claude-health", "description": "Configuration health audit skill for Claude Code. Audits CLAUDE.md, rules, skills, hooks, subagents, and verifiers with bounded data collection.",
"version": "0.25.0", "description": "Datadog API CLI with 49 command groups, 300+ subcommands. Skills and domain agents for monitoring, logs, APM, security, and infrastructure.", "email": "support@datadoghq.com"
Analyzes ANY input to find, improve, or create the right skill. Start with least privilege (, , , , ). Only add higher-risk tools when explicitly required:
An orchestrator booster that automatically fetches GitHub issues, spawns AI sub-agents to implement fixes, opens pull requests, and manages review feedback. Ideal for teams looking to automate bug triage and fix workflows.
"name": "research-companion", "description": "Strategic research thinking agents — idea evaluation, project triage, and structured brainstorming inspired by Carlini's research methodology", "name": "Andre Huang",
Quoroom is an experimental open-source framework for building local AI agent systems with a Queen-Workers-Quorum architecture, designed for researchers and developers exploring multi-agent AI patterns with Claude and other LLMs.
1. Preserve custom rules from existing .gitignore 3. On auth error (401), retry with 4. Re-add preserved custom rules
A planning-first agent that generates structured task breakdowns before execution, helping developers clarify scope and avoid missteps on complex code operations. Ideal for teams using Claude in agentic workflows.
"name": "langchain-skills", "description": "Agent skills for building agents with LangChain, LangGraph, and Deep Agents", "name": "LangChain",
This skill documents how to run the Parchi relay daemon, connect the browser extension as an agent, and use the CLI to drive browser automation. 1. Build everything: 2. Start the relay daemon (terminal A):
BlockRun MCP Server enables Claude users to access 30+ AI models through x402 micropayments without requiring API keys. This benefits developers who want flexible model access and cost-efficient AI inference across multiple providers.
This booster provides expert guidance for developing, debugging, and optimizing Azure AI Document Intelligence applications, covering architecture, security, best practices, and deployment patterns. Developers building document processing solutions on Azure will benefit from its comprehensive troubleshooting and design pattern knowledge.
VTCode is a system prompt designed to enhance a semantic AI coding agent for terminal-based development environments, providing clearer instructions and error handling for developers using Claude, Cursor, Windsurf, or ChatGPT.
"name": "ensue-memory", "description": "Persistent memory layer for AI agents via Ensue Memory Network", "email": "founders@ensue.dev"
Heuristic scoring (no AI key configured).
This skill parses natural language shopping queries to extract structured product requirements like attributes, price limits, and specifications for e-commerce agents. It benefits developers building AI-powered shopping assistants and agents that need intelligent query understanding.
"name": "power-bi-agentic-development", "version": "0.19.0", "description": "A marketplace for skills and tools for agentic Power BI development.",
A CLI skill for interacting with Obsidian vaults—read, create, search, and manage notes, tasks, and properties directly from the command line, plus plugin/theme development support. Useful for developers and power users who want to automate vault operations and debug Obsidian extensions.
wraps your coding agent (Claude Code, Codex, OpenCode) in composable workflows: review loops, repeat passes, parallel races, and task-list orchestration. Operators compose left to right. Loop operators wrap everything to their left. Custom review/gate prompts (positional shorthand):
