Use this agent when you need to create automated browser tests using Playwright. Examples: <example>Context: User wants to test a login flow on their web application. user: 'I need a test that logs into my app at localhost:3000 with username [email protected] and password 123456, then verifies the dashboard page loads' assistant: 'I'll use the generator agent to create and validate this login test for you' <commentary> The user needs a specific browser automation test created, which is exactly what the generator agent is designed for. </commentary></example><example>Context: User has built a new checkout flow and wants to ensure it works correctly. user: 'Can you create a test that adds items to cart, proceeds to checkout, fills in payment details, and confirms the order?' assistant: 'I'll use the generator agent to build a comprehensive checkout flow test' <commentary> This is a complex user journey that needs to be automated and tested, perfect for the generator agent. </commentary></example>
Use this agent when you need to debug and fix failing Playwright tests. Examples: <example>Context: A developer has a failing Playwright test that needs to be debugged and fixed. user: 'The login test is failing, can you fix it?' assistant: 'I'll use the healer agent to debug and fix the failing login test.' <commentary> The user has identified a specific failing test that needs debugging and fixing, which is exactly what the healer agent is designed for. </commentary></example><example>Context: After running a test suite, several tests are reported as failing. user: 'Test user-registration.spec.ts is broken after the recent changes' assistant: 'Let me use the healer agent to investigate and fix the user-registration test.' <commentary> A specific test file is failing and needs debugging, which requires the systematic approach of the playwright-test-healer agent. </commentary></example>
Use this agent when you need to create comprehensive test plan for a web application or website. Examples: <example>Context: User wants to test a new e-commerce checkout flow. user: 'I need test scenarios for our new checkout process at https://mystore.com/checkout' assistant: 'I'll use the planner agent to navigate to your checkout page and create comprehensive test scenarios.' <commentary> The user needs test planning for a specific web page, so use the planner agent to explore and create test scenarios. </commentary></example><example>Context: User has deployed a new feature and wants thorough testing coverage. user: 'Can you help me test our new user dashboard at https://app.example.com/dashboard?' assistant: 'I'll launch the planner agent to explore your dashboard and develop detailed test scenarios.' <commentary> This requires web exploration and test scenario creation, perfect for the planner agent. </commentary></example>
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Marketplace de plugins pour Claude Code, fournissant des outils et workflows de développement.
| Plugin | Description | Composants |
|---|---|---|
| security | Bloque l'accès aux fichiers sensibles + scanne les commits pour détecter les secrets + circuit breaker | Hook, Utility |
| notifications-system | Sons système et notifications OS | Hook |
| git | Commits conventionnels + push securisé (bloque main/master) | Skills |
| playwright | MCP Playwright + agents tests E2E (planner, generator, healer) | MCP, Agents |
| statusline | Statusline avec suivi des coûts, git et support multi-plans | Command, Script |
| experts | Agent architecte pour analyse de code et évolutions | Agent |
| claude-factory | Meta-plugin pour créer des outils Claude Code + dream consolidation | Skills |
| frustration-detector | Détecte la frustration et adapte le style de Claude (moins de blabla, plus d'action) | Hook |
/plugin marketplace add <YOUR_GIT_URL>
Ou via le mode interactif :
/plugin
# Aller dans l'onglet "Marketplaces" > "Add marketplace"
# Coller l'URL de votre repository git
Interactif (recommandé) :
/plugin
# Aller dans l'onglet "Discover" et sélectionner les plugins à installer
Installation directe :
/plugin install security@angelo-plugins
/plugin install notifications-system@angelo-plugins
/plugin install git@angelo-plugins
/plugin install playwright@angelo-plugins
/plugin install statusline@angelo-plugins
/plugin install experts@angelo-plugins
/plugin install claude-factory@angelo-plugins
/plugin install frustration-detector@angelo-plugins
Ajouter dans le .claude/settings.json de votre projet pour auto-configurer tous les membres de l'équipe :
{
"extraKnownMarketplaces": {
"angelo-plugins": {
"source": {
"source": "git",
"url": "<YOUR_GIT_URL>"
}
}
},
"enabledPlugins": {
"security@angelo-plugins": true,
"git@angelo-plugins": true
}
}
| Commande | Description |
|---|---|
/plugin | Ouvrir le gestionnaire de plugins interactif |
/plugin install name@marketplace | Installer un plugin |
/plugin uninstall name@marketplace | Supprimer un plugin |
/plugin enable name@marketplace | Activer un plugin désactivé |
/plugin disable name@marketplace | Désactiver sans supprimer |
/plugin marketplace list | Lister les marketplaces enregistrées |
/plugin marketplace update | Mettre à jour les métadonnées |
Deux protections automatiques via hooks PreToolUse :
.env, credentials.json, .pem, etc.git commit pour détecter ~30 types de secrets (Anthropic, OpenAI, AWS, GitHub, GitLab, Slack, Stripe...) et bloque si des clés API ou tokens sont trouvés dans les fichiers stagés.Aucune commande nécessaire - fonctionne automatiquement via hook.
Note sécurité : Ce plugin utilise des hooks
PreToolUseplutôt que lesdenyrules desettings.json. Les deny rules ont des bugs connus où elles sont parfois ignorées. Les hooks avec exit code 2 garantissent un blocage fiable.
/commit
# Analyse les changements et cree un commit conventionnel avec le Jira de la branche
/push
# Pousse les commits (BLOQUE si sur main/master)
/statusline-setup
# Configure la statusline avec suivi des coûts, git, et support multi-plans (Pro, Max5, Max20, Pay-as-you-go)
Nécessite jq et optionnellement ccusage.
# L'agent se déclenche sur les questions d'architecture
Analyse l'architecture du module orders
Comment découper ce service monolithique ?
Quelle est la dette technique de ce projet ?
Agent Opus pour analyses approfondies et propositions d'évolution.
Le plugin inclut un serveur MCP Playwright et 3 agents spécialisés pour les tests E2E :
npx claudepluginhub lingelo/marketplace-claude-code --plugin playwrightMeta-plugin for creating Claude Code tools: skills, hooks, agents, commands, rules, CLAUDE.md maintenance, audit, and offline documentation reference.
Detects developer frustration and adapts Claude's response style (less talk, more action)
Collection d'agents experts spécialisés (architecte, etc.)
Blocks access to sensitive files and scans git commits for leaked secrets
Setup wizard for hell0github/claude-statusline - supports subscriptions (Pro, Max) and API Usage (pay-as-you-go) with automatic cleanup
Advanced Playwright skills for end-to-end testing, test architecture, and test automation best practices.
Production-grade Playwright testing toolkit. Generate tests from specs, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55+ ready-to-use templates, 3 specialized agents, smart reporting that plugs into your existing workflow.
Playwright E2E test debugging and interactive browser exploration. Runs tests with action capture (DOM snapshots, network, console, screenshots), diagnoses failures, and provides browser tools for navigating, clicking, and inspecting pages through ARIA snapshots.
Quality assurance - E2E testing, PR review, browser automation
End-to-end test execution and recording for web applications
End-to-end test automation with Playwright, Cypress, and Selenium for browser-based testing