Recently added

Aug 25, 2026

1. minimal-plugin757stars

   A minimal plugin

   Codex
2. malicious-skill-plugin757stars

   Fixture with a dangerous local skill definition

   Codex
3. example-good-plugin757stars

   A well-structured example plugin. Includes 1 skill.

   Codex1 skill
4. claude-example-plugin757stars

   Example Claude plugin package

   Claude Code
5. pstack0stars

   if you want to go fast, go deep first. pstack helps you write less, but higher quality code. rigorous agent workflows you can parallelize with confidence. Claude Code port of cursor/plugins/pstack.

   Claude Code44 skills
6. slash0stars

   Skills et automatismes de traitement des tickets Linear SLI : parcours du ticket, constat partagé, jeu de données de recette, taille et découpage des pull requests, rédaction des écrits lus par un humain — écrits GitHub et livrables longs, ancrage du navigateur.

   Claude Code2 skills1 MCP server
7. mattpocock-skills3stars

   mattpocock-skills is an open-source Claude Code plugin indexed from GitHub. Review its manifest and source before installing.

   Claude Code
8. mattpocock-skills3stars

   mattpocock-skills is an open-source Claude Code plugin indexed from GitHub. Review its manifest and source before installing.

   Claude Code
9. mh3stars

   A Claude Code harness that composes mattpocock-skills instead of duplicating it. Nine computational deny/ask gates (irrecoverable commands, subagent git guard, subagent spawn guard, task-complete separation, test integrity, config-write guard, secret-content scan, codex-setup guard, routine-trigger guard) plus a SubagentStop verdict-check gate, a 4 KB METHODOLOGY injected at SessionStart, and memory-lint for the auto-memory store.

   Claude Code
10. quorum0stars

    A four-step delivery pipeline (plan, build, multi-lens review, adjudication) with behavioral regression tests and CI gating.

    Claude Code7 skills
11. agent-skills0stars

    Personal, agent-agnostic collection of reusable skills.

    Claude Code6 skills
12. brain-dev0stars

    Rootcause Brain Dev skills for local checks, safe cross-computer Git sync, rc ask validation, production-run debugging, health/fleet review, and exact-SHA publish workflows. Brain-dir-relative; no private RootCause source needed.

    Codex12 skills
13. signal1stars

    Plain English harness. States the budget before the agent writes, and reads what came back.

    Claude Code3 skills
14. pest1stars

    Pest testing suite skills. Philosophy, organization, factories, datasets, arch testing, mocking decisions.

    Claude Code11 skills
15. panel1stars

    Adversarial agent teams. Verification that cannot be self-issued. Standalone; pairs well with kernel.

    Claude Code5 skills
16. laravel-playbook1stars

    The package author's playbook. Ecosystem-wide patterns for crafting, shipping, and sustaining pinnacle Laravel packages.

    Claude Code29 skills
17. laravel-ddd1stars

    Laravel DDD patterns. Opinionated domain-driven design with Actions, DTOs, QueryBuilders, and decision heuristics. Standalone; pairs well with kernel.

    Claude Code47 skills
18. kernel1stars

    Universal cognitive kernel. Stack-agnostic thinking patterns, memory management, and planning tools. The foundation for all Craftsman plugins.

    Claude Code39 skills
19. floor1stars

    Where work happens. A run is one attempt at one work item, held outside every repository it changes.

    Claude Code1 skill
20. wenlan51stars

    A living knowledge base your agents build as they work. What they learn becomes source-cited wiki pages that refresh between sessions, so each new thread starts from your latest work.

    Claude Code11 skills1 MCP server
21. wenlan51stars

    A living knowledge base your agents build as they work. What they learn becomes source-cited wiki pages that refresh between sessions, so each new thread starts from your latest work.

    Codex11 skills1 MCP server
22. core1stars

    core is an open-source Claude Code plugin indexed from GitHub. Review its manifest and source before installing.

    Claude Code
23. execution-observation1stars

    execution-observation is an open-source Claude Code plugin indexed from GitHub. Review its manifest and source before installing.

    Claude Code
24. on-the-record1stars

    The orchestration loop for contract v3: draft issues from the user's words, spawn role sessions (core plugins + role rulebook, agent account, issue-<n>/<role> branch), explain the PRs that come back, and relay the user's decisions — comments, review Approve, merge — with the user's own account, per conversation.

    Claude Code
25. ux-engineering1stars

    The ux-engineering role on contract v3: 디자인 결정 → 토큰/규칙 시스템화. use_when: 화면 스펙이 여러 개 쌓여 시스템화가 필요할 때. Hand-off: 브랜드 정체성 결정이 필요하면 → brand-design; 접근성 기준 미달이면 → accessibility.

    Claude Code
26. technical-writing1stars

    The technical-writing role on contract v3: 독자가 알아야 할 것을 어떻게 구조화할지. use_when: 외부 공개 문서가 필요할 때. Hand-off: 개발자 대상 온보딩이면 → devrel.

    Claude Code
27. security-threat-model1stars

    The security-threat-model role on contract v3: 신뢰 경계의 위협 표면. use_when: 스펙에 신뢰 경계·인증·민감데이터가 걸릴 때. Hand-off: 구현 단계 취약점 점검은 → secure-coding; 법적 노출이면 → legal-compliance.

    Claude Code
28. secure-coding1stars

    The secure-coding role on contract v3: 구현이 공격에 견디는가. use_when: 인증/입력처리 코드 랜딩 후. Hand-off: 설계 단계 위협표면 재검토가 필요하면 → security-threat-model.

    Claude Code
29. sales1stars

    The sales role on contract v3: 리드/기회를 어떻게 진행시킬지. use_when: 영업 프로세스 설계가 걸릴 때. Hand-off: 메시지/포지셔닝 자체는 → marketing.

    Claude Code
30. risk-management1stars

    The risk-management role on contract v3: 전사 리스크 노출이 허용 범위인가. use_when: 재무/운영/전략 리스크가 걸릴 때 (feasibility보다 넓은 범위). Hand-off: 개별 법규 컴플라이언스 세부는 → legal-compliance.

    Claude Code
31. pricing1stars

    The pricing role on contract v3: 얼마를, 어떤 구조로 받을지. use_when: 신규 가격 정책이 걸릴 때. Hand-off: 단위경제 성립 여부 재확인은 → finance-unit-economics.

    Claude Code
32. pr-communications1stars

    The pr-communications role on contract v3: 메시지가 외부에 어떻게 읽힐지. use_when: 외부 커뮤니케이션이 걸릴 때. Hand-off: 캠페인 성격 메시지는 → marketing.

    Claude Code
33. performance-engineering1stars

    The performance-engineering role on contract v3: 부하/지연 목표를 만족하는가. use_when: 성능 예산이 걸린 설계/회귀일 때. Hand-off: 용량 증설 타이밍이 걸리면 → capacity-planning.

    Claude Code
34. partnerships-bd1stars

    The partnerships-bd role on contract v3: 파트너십이 구조적으로 성립하는가. use_when: 제휴/BD 딜 구조가 걸릴 때. Hand-off: 법적 계약 검토는 → legal-compliance.

    Claude Code
35. ml-engineering1stars

    The ml-engineering role on contract v3: 모델을 서비스로 안정적으로 서빙 가능한가. use_when: 모델 서빙 표면이 걸릴 때. Hand-off: 학습 데이터 파이프라인이면 → data-engineering.

    Claude Code
36. marketing1stars

    The marketing role on contract v3: 어떤 메시지로 어떤 채널에 도달할지. use_when: 캠페인/포지셔닝이 걸릴 때. Hand-off: 퍼널 성과 해석은 → growth-analytics.

    Claude Code
37. market-analysis1stars

    The market-analysis role on contract v3: 경쟁 구도에서 이 스펙이 서는가. use_when: product 스펙 확정 후, 경쟁 구도가 걸린 결정일 때. Hand-off: 가격 정책이 걸리면 → pricing; 포지셔닝 메시지가 걸리면 → marketing.

    Claude Code
38. localization1stars

    The localization role on contract v3: 다른 로케일에서도 산출물이 성립하는가. use_when: i18n 대상 표면이 걸릴 때. Hand-off: 카피 원문 자체를 다시 써야 하면 → content-design.

    Claude Code
39. legal-compliance1stars

    The legal-compliance role on contract v3: 이 스펙/처리가 법·규제를 통과하는가. use_when: 개인정보·라이선스·계약이 걸릴 때. Hand-off: 전사 리스크 노출 규모 판단은 → risk-management.

    Claude Code
40. growth-analytics1stars

    The growth-analytics role on contract v3: 퍼널 병목과 실험 결과가 실제 개선인지. use_when: 퍼널 분석 또는 A/B 실험 해석이 걸릴 때. Hand-off: 캠페인 메시지 변경이 필요하면 → marketing.

    Claude Code
41. finance-unit-economics1stars

    The finance-unit-economics role on contract v3: 단위경제상 성립하는가. use_when: 가격/비용 구조가 걸린 결정일 때. Hand-off: 실제 가격 숫자 결정은 → pricing.

    Claude Code
42. devrel1stars

    The devrel role on contract v3: 외부 개발자가 이 표면을 채택할 수 있는가. use_when: 외부 개발자 대상 API/SDK가 걸릴 때. Hand-off: API 표면 자체 재설계는 → api-design.

    Claude Code
43. data-modeling1stars

    The data-modeling role on contract v3: 데이터를 어떤 관계/스키마로 모델링할지. use_when: 스키마 신설/변경이 걸릴 때. Hand-off: 파이프라인 이동/변환이 걸리면 → data-engineering.

    Claude Code
44. data-engineering1stars

    The data-engineering role on contract v3: 파이프라인이 데이터를 안정적으로 이동·변환하는가. use_when: 파이프라인 신설/변경이 걸릴 때. Hand-off: 스키마 설계 자체는 → data-modeling.

    Claude Code
45. customer-support1stars

    The customer-support role on contract v3: 문의를 어떤 우선순위/SLA로 처리할지. use_when: CS 플로우/SLA 설계가 걸릴 때. Hand-off: 반복 문의가 제품 결함이면 → product-discovery.

    Claude Code
46. content-design1stars

    The content-design role on contract v3: 문구가 사용자의 실제 결정을 돕는가. use_when: 플로우에 새 카피/마이크로카피가 걸릴 때. Hand-off: 화면/플로우 구조 자체가 바뀌어야 하면 → interaction-design.

    Claude Code
47. brand-design1stars

    The brand-design role on contract v3: 브랜드 정체성이 시각적으로 일관되는가. use_when: 브랜드 자산 신설/변경이 걸릴 때. Hand-off: 토큰 시스템화 구현은 → ux-engineering.

    Claude Code
48. architecture1stars

    The architecture role on contract v3: 컴포넌트 경계·의존 방향. use_when: 새 모듈 경계나 기존 경계 변경이 걸릴 때. Hand-off: 인터페이스 형태 세부는 → api-design; 성능 예산이 걸리면 → performance-engineering.

    Claude Code
49. api-design1stars

    The api-design role on contract v3: 서비스 경계의 인터페이스 형태. use_when: 여러 소비자가 걸리는 API 표면을 설계/변경할 때. Hand-off: 컴포넌트 경계 자체가 바뀌면 → architecture; 스키마 신설/변경이면 → data-modeling.

    Claude Code
50. accessibility1stars

    The accessibility role on contract v3: 화면/토큰이 WCAG를 만족하는가. use_when: 신규 인터랙션 패턴·색상 토큰 도입 시. Hand-off: 카피 자체의 이해 가능성이면 → content-design.

    Claude Code