Skip to content
Back to search

wasp-nest

SkillGitHubIncomplete

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/legioncodeinc/vibe-coding-tools with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/legioncodeinc/vibe-coding-tools'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/legioncodeinc--vibe-coding-tools/badge.svg)](/listings/legioncodeinc--vibe-coding-tools)

HTML

<a href="/listings/legioncodeinc--vibe-coding-tools"><img src="/api/listings/legioncodeinc--vibe-coding-tools/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 117 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "wasp-nest",
  3. "owner": {
  4. "name": "Legion Code Inc."
  5. },
  6. "metadata": {
  7. "description": "The Wasp Nest: core plus add-on packs.",
  8. "version": "3.0.1"
  9. },
  10. "plugins": [
  11. {
  12. "name": "wasp-nest-core",
  13. "source": "./plugins/wasp-nest-core",
  14. "description": "The Wasp Nest core. Install first."
  15. },
  16. {
  17. "name": "browser-and-app-testing-tools",
  18. "source": "./plugins/browser-and-app-testing-tools",
  19. "description": "Automate browsers, capture live apps and measure Lighthouse/PageSpeed behavior."
  20. },
  21. {
  22. "name": "website-audit-tools",
  23. "source": "./plugins/website-audit-tools",
  24. "description": "Audit a public website with crawl, SEO, accessibility, conversion and evidence-backed reports."
  25. },
  26. {
  27. "name": "code-audit-tools",
  28. "source": "./plugins/code-audit-tools",
  29. "description": "Audit repositories and app security, measure bloat, inspect branches and plan remediation."
  30. },
  31. {
  32. "name": "documentation-tools",
  33. "source": "./plugins/documentation-tools",
  34. "description": "Refresh, extract, publish and package documentation from real sources."
  35. },
  36. {
  37. "name": "web-development-tools",
  38. "source": "./plugins/web-development-tools",
  39. "description": "Build web interfaces and sites with React, Svelte, design systems and accessible components."
  40. },
  41. {
  42. "name": "backend-and-desktop-tools",
  43. "source": "./plugins/backend-and-desktop-tools",
  44. "description": "Implement TypeScript, Python, Go, Rust, native apps, APIs and terminal workflows."
  45. },
  46. {
  47. "name": "data-and-ai-tools",
  48. "source": "./plugins/data-and-ai-tools",
  49. "description": "Design data, retrieval, AI runtime, model tooling and agent operations."
  50. },
  51. {
  52. "name": "platform-and-release-tools",
  53. "source": "./plugins/platform-and-release-tools",
  54. "description": "Integrate authentication, payments, analytics, messaging and production delivery."
  55. },
  56. {
  57. "name": "growth-and-customer-tools",
  58. "source": "./plugins/growth-and-customer-tools",
  59. "description": "Research buyers, acquire leads, follow up, support customers and grow accounts."
  60. },
  61. {
  62. "name": "business-and-product-tools",
  63. "source": "./plugins/business-and-product-tools",
  64. "description": "Form and run a company, discover product needs, hire teams and improve delivery."
  65. },
  66. {
  67. "name": "media-and-creative-tools",
  68. "source": "./plugins/media-and-creative-tools",
  69. "description": "Create consented photography and integrate voice and video production."
  70. },
  71. {
  72. "name": "highlevel",
  73. "source": "./plugins/highlevel",
  74. "description": "Integrate HighLevel, build with AI Studio and map exported workflows."
  75. },
  76. {
  77. "name": "littlebird-toolkit",
  78. "source": "./plugins/littlebird-toolkit",
  79. "description": "Turn Littlebird memory into evidence-backed operating work."
  80. },
  81. {
  82. "name": "content-intelligence",
  83. "source": "./plugins/content-intelligence",
  84. "description": "Find and verify current repository/news topics and prepare voice-matched drafts."
  85. },
  86. {
  87. "name": "app-primer-zero",
  88. "source": "./plugins/app-primer-zero",
  89. "description": "Prepare an app library, contracts, schema baseline and a wave handoff before building."
  90. },
  91. {
  92. "name": "developer-learning-tools",
  93. "source": "./plugins/developer-learning-tools",
  94. "description": "Explain technical sources with source-grounded analogies and learner checks."
  95. },
  96. {
  97. "name": "software-economics-tools",
  98. "source": "./plugins/software-economics-tools",
  99. "description": "Model supplied software economics and costs with explicit scenarios and evidence."
  100. },
  101. {
  102. "name": "infrastructure-decision-tools",
  103. "source": "./plugins/infrastructure-decision-tools",
  104. "description": "Prepare platform assets and account dependencies without implicit setup actions."
  105. },
  106. {
  107. "name": "repository-modernization-tools",
  108. "source": "./plugins/repository-modernization-tools",
  109. "description": "Compose repository baseline, safe refactoring and contributor onboarding through selected specialist owners."
  110. },
  111. {
  112. "name": "product-studio",
  113. "source": "./plugins/product-studio",
  114. "description": "Turn an idea into a buildable plan: product strategy, Claude-Design-grade UX, a PRD map, a wave plan and a Definition of Done."
  115. }
  116. ]
  117. }
README.md · README · 227 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <!-- Generated from the source publication template. Edit the source template, not this public copy. -->
  2. <div align="center">
  3. <a href="assets/the-wasp-nest.png"><img alt="The Wasp Nest, a crowned wasp above a glowing honeycomb" src="assets/the-wasp-nest.jpg" width="100%"></a>
  4. # The Wasp Nest
  5. ### Get the Git life.
  6. **184 specialist Drones, 223 Stingers, commands, hooks, and rules across 21 installable plugins.**
  7. Give your coding assistant the people, playbooks, and project memory it needs to build.
  8. [![Public release](https://img.shields.io/github/v/release/legioncodeinc/vibe-coding-tools?label=release)](https://github.com/legioncodeinc/vibe-coding-tools/releases)
  9. [![Release workflow](https://img.shields.io/github/actions/workflow/status/legioncodeinc/vibe-coding-tools/release.yml?branch=main&label=release%20build)](https://github.com/legioncodeinc/vibe-coding-tools/actions/workflows/release.yml)
  10. [![License](https://img.shields.io/github/license/legioncodeinc/vibe-coding-tools?branch=main)](LICENSE.md)
  11. </div>
  12. <div align="center">
  13. <a href="https://www.ospry.ai">
  14. <picture>
  15. <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/legioncodeinc/brands/main/ospry/logos/png/core-assets/transparent/horizontal-white-1024.png">
  16. <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/legioncodeinc/brands/main/ospry/logos/png/core-assets/transparent/horizontal-ink-1024.png">
  17. <img alt="OSPRY" src="https://raw.githubusercontent.com/legioncodeinc/brands/main/ospry/logos/png/core-assets/transparent/horizontal-ink-1024.png" width="260">
  18. </picture>
  19. </a>
  20. <sub>Want to know what will actually drive more revenue? <strong><a href="https://www.ospry.ai">OSPRY</a></strong> is the insight engine built for exactly that.</sub>
  21. </div>
  22. ## Start here
  23. Install [Claude Code](https://code.claude.com/docs/en/overview) or [Codex](https://developers.openai.com/codex), then add the public marketplace. In Claude Code, enter these in the assistant's command prompt:
  24. ```text
  25. /plugin marketplace add legioncodeinc/vibe-coding-tools
  26. /plugin install wasp-nest-core@wasp-nest
  27. ```
  28. In a terminal with Codex installed, add the same marketplace and select the core in the plugin browser:
  29. ```bash
  30. codex plugin marketplace add legioncodeinc/vibe-coding-tools
  31. codex plugin add wasp-nest-core@wasp-nest
  32. ```
  33. The v3 layout has a required Core and the optional plugins declared in its current catalog. Purge the previous Wasp Nest installation before installing it. Keep Core enabled and select each workflow's prerequisites.
  34. Choose the packs your work needs. Claude skills use their plugin namespace, such as `/wasp-nest-core:get-started-stinger`; Codex shows skills and command wrappers. Native Codex Drone roles require Core's trusted hook and an explicit registry of enabled package roots. The local installer writes that registry; a marketplace install alone is not proven to do so. Review the selection before trusting `/hooks` and starting a new session. See [harness capabilities](learn/reference/HARNESS-CAPABILITIES.md).
  35. Open the repository you want to work on and ask:
  36. ```text
  37. Use the Get Started Stinger to inspect this repository. Explain the home instruction setup and the project Library setup, ask before changing either, and show me the resulting diff and setup report.
  38. ```
  39. The first-session hook checks home and project setup locks on supported local hosts. Missing setup prompts an offer. Existing code gets a Knowledge pass before Library setup completes. [Read Getting Started](learn/guides/GETTING-STARTED.md) before accepting either offer.
  40. ## The problem this fixes
  41. Your assistant can write code. It still needs your product facts, past decisions and definition of done.
  42. Drones own bounded specialties. Stingers carry methods, examples and cited research. The Library keeps knowledge, plans, issue fixes and shared contracts for the next agent. You can check the work against written decisions.
  43. ## The Library is the workbench
  44. The Library holds current facts and future plans in your project. Get Started offers setup after consent; Knowledge documents existing code first. Human-only `library/notes/` is not agent input.
  45. | Record | Write it when | Who helps |
  46. | --- | --- | --- |
  47. | Knowledge and ADR | You need current system truth or the reason for an architecture choice. | Knowledge or ADR Writing Stinger. |
  48. | PRD | You plan new behavior and need observable acceptance criteria. | Library Stinger. |
  49. | IRD | A tracked bug needs a bounded fix and proof, using its issue number. | Library Stinger. |
  50. | `CTR-###` | Two or more plans depend on the same API, event, data shape, permission, or state transition. | Contract Writing drafts; you accept the exact revision; Library pins it in each affected PRD. |
  51. Learn [why the Library exists](learn/concepts/WHY-THE-LIBRARY.md), [write a PRD](learn/guides/WRITE-A-PRD.md) or [IRD](learn/guides/WRITE-AN-IRD.md), and [agree on a CTR](learn/guides/WRITE-A-CTR.md). Draft contracts block dependent work.
  52. ## From request to reviewed code
  53. ```mermaid
  54. flowchart TD
  55. A["New request"] --> B{"What kind of work?"}
  56. B -- New product --> PS["/plan-product: strategy, design, wave plan, Definition of Done"]
  57. PS --> P
  58. B -- New behavior --> P["Library writes a PRD with acceptance criteria"]
  59. B -- Tracked bug --> I["Library writes an IRD"]
  60. B -- Scoped task --> R["Call /pest-controller"]
  61. P --> C{"Shared boundary across plans?"}
  62. C -- Yes --> D["Contract Writing drafts CTR-###"]
  63. D --> E{"Exact revision accepted?"}
  64. E -- No --> W["Dependent work waits; unrelated work continues"]
  65. E -- Yes --> PIN["Library pins the revision in each PRD"]
  66. PIN --> S["Call /smoke-it"]
  67. C -- No --> S
  68. I --> R
  69. S --> L["Acceptance ledger and the approved wave plan"]
  70. L --> CODE["Drones read Stingers, code, and test"]
  71. R --> CODE
  72. CODE --> V["Verify against the PRD, IRD, or task"]
  73. V --> G["Security then quality; Ship Gate on demand"]
  74. G --> H["Owner authorizes commit and push"]
  75. H --> PR["Pull request, CI, and review"]
  76. ```
  77. `/smoke-it` is the full PRD execution path. It selects Drones from the roster itself, so you do not need to call `/pest-controller` first. Use `/pest-controller` to route a bounded task or IRD fix. Smoke It includes security and quality close-out; `/ship-gate` is the on-demand gate for a scoped diff. Neither command grants permission to commit, push, or deploy.
  78. For parallel PRDs, one accepted contract revision is the handoff:
  79. ```mermaid
  80. flowchart LR
  81. B[Shared boundary found] --> C[Contract Writing drafts CTR-###]
  82. C --> A{Exact revision accepted?}
  83. A -- No --> W[Dependent work waits]
  84. A -- Yes --> P1[Library pins PRD A]
  85. A -- Yes --> P2[Library pins PRD B]
  86. P1 --> X[Provider work]
  87. P2 --> Y[Consumer work]
  88. X --> T[Checks against same CTR revision]
  89. Y --> T
  90. ```
  91. A Draft or disputed contract blocks the dependent boundary. [The learning path](learn/README.md) has the document-authoring guides, worked example, and more diagrams.
  92. ## What to call
  93. Short Core commands use `/wasp-nest-core:` in native Claude. Optional commands show their owning prefix below. Use your client's exact selector; local home installations also expose flat commands.
  94. | Situation | Ask for | What happens |
  95. | --- | --- | --- |
  96. | New or existing repository has no Library | `get-started-stinger` | Offers home and project setup separately, preserves existing work, and reports its changes. |
  97. | Plan a new product before building it | [`/product-studio:plan-product`](plugins/product-studio/commands/plan-product.md) | Interviews you for the strategy, designs the UX with prototypes and a Claude Design round trip, then writes the PRD map, wave plan and Definition of Done, with your approval at each stage. |
  98. | Planned feature | `library-stinger`, then `/smoke-it` once the PRD is ready | Defines criteria before code, then tracks implementation and verification. |
  99. | Shared provider and consumer behavior | `contract-writing-stinger` before dependent PRDs finish | Records a CTR, requests acceptance, and hands the revision to Library for PRD pins. |
  100. | Tracked defect or bounded task | `library-stinger` for an IRD if tracked, then `/pest-controller` | Routes a scoped fix to an armed Drone. |
  101. | Standalone pre-ship check | `/ship-gate` | Reviews the diff in order: security, quality, repository health, then your decision. |
  102. | Founder, investor, sales, service or public documents | [`/documentation-tools:library-packets`](learn/guides/DOCUMENT-WORKFLOWS.md#library-packets-share-what-the-sources-support) | Reads a library and produces supported Markdown, Word, branded PDF and citations. |
  103. | Prepare a new or partial app for a build | [`/app-primer-zero:app-primer-zero`](learn/guides/DOCUMENT-WORKFLOWS.md#app-primer-zero-prepare-the-build) | Establishes current state, drafts contracts and schema, then hands off a bounded build plan. |
  104. | Refresh stale repository knowledge across many files | [`/documentation-tools:kb-refresh`](learn/guides/DOCUMENT-WORKFLOWS.md#kb-refresh-bring-repository-knowledge-current) | Rechecks code citations, updates owned docs, and reports drift and suspected code issues. Full discovery also needs Code Audit. |
  105. | Assess a public website | [`/website-audit-tools:perform-website-audit`](plugins/website-audit-tools/commands/perform-website-audit.md) | Runs intake, site evidence, findings, scores and branded reports. |
  106. | Assess a codebase | [`/code-audit-tools:audit-my-code`](plugins/code-audit-tools/commands/audit-my-code.md) | Selects an audit tier and produces evidence, a brief and any approved remediation plan. |
  107. | Capture a running app | [`/browser-and-app-testing-tools:webapp-capture`](plugins/browser-and-app-testing-tools/commands/webapp-capture.md) | Creates scoped screenshots, demos or a visual inventory after intake and a dry run. |
  108. | Manage several implementation sessions | [`/data-and-ai-tools:tars`](plugins/data-and-ai-tools/commands/tars.md) | TARS manages the work, CASE challenges and resolves scoped decisions, and KIPP runs the Feature Desk. All three require Claude Code Desktop. |
  109. These are Claude entry points. Other clients use supported Stingers or command wrappers. TARS, CASE and KIPP have no Codex, Cursor or Cowork fallback; they require Claude Code Desktop. Invocation does not authorize external actions.
  110. Keep Core installed alongside each owning plugin. [Choose a document workflow](learn/guides/DOCUMENT-WORKFLOWS.md) for prerequisites, sample requests and the difference between preparing an app, refreshing its knowledge and explaining it to readers. Use `/wasp-nest-core:forge` for a new reusable component; public correction requests belong in the issue tracker below.
  111. ## The parts, in plain English
  112. | Piece | What it is |
  113. | --- | --- |
  114. | **Drone** | A specialist agent with a bounded responsibility. |
  115. | **Stinger** | The procedure and reference material a Drone reads before working. Some Stingers are standalone orchestrators. |
  116. | **Pest Controller** | The router that chooses and arms the right Drone. |
  117. | **Product Studio** | The planning plugin: strategy, UX design, and the build plan (PRD map, wave plan, Definition of Done) before any PRD is written. |
  118. | **Smoke It** | The execution workflow that drives PRD criteria to verified completion, in the approved wave order. |
  119. | **Rule** | A persistent operating boundary for supported harnesses. |
  120. | **Hook** | A lifecycle check, including the consent-based first-session setup offer. |
  121. The Drone and Stinger pairing is enforced by the source validator. A missing pairing is not silently shipped.
  122. ## What ships
  123. Marketplace release **v3.0.1**. The core and add-on packs have independent manifest versions; counts and descriptions below are read from the built plugins, not maintained by hand.
  124. | Plugin | Version | Stingers | Drones | What it does |
  125. | --- | --- | ---: | ---: | --- |
  126. | [wasp-nest-core](plugins/wasp-nest-core/README.md) | 3.0.1 | 18 | 14 | The Wasp Nest core: shared Drones and Stingers, orchestration commands, rules, and hooks. |
  127. | [app-primer-zero](plugins/app-primer-zero/README.md) | 3.0.1 | 1 | 0 | Prepare an app library, contracts, schema baseline and a wave handoff before building. |
  128. | [backend-and-desktop-tools](plugins/backend-and-desktop-tools/README.md) | 3.0.1 | 10 | 10 | Implement TypeScript, Python, Go, Rust, native apps, APIs and terminal workflows. |
  129. | [browser-and-app-testing-tools](plugins/browser-and-app-testing-tools/README.md) | 3.0.1 | 4 | 4 | Automate browsers, capture live apps and measure Lighthouse/PageSpeed behavior. |
  130. | [business-and-product-tools](plugins/business-and-product-tools/README.md) | 3.0.1 | 15 | 15 | Form and run a company, discover product needs, hire teams and improve delivery. |
  131. | [code-audit-tools](plugins/code-audit-tools/README.md) | 3.0.1 | 12 | 11 | Audit repositories and app security, measure bloat, inspect branches and plan remediation. |
  132. | [content-intelligence](plugins/content-intelligence/README.md) | 3.0.1 | 2 | 0 | Find and verify current repository/news topics and prepare voice-matched drafts. |
  133. | [data-and-ai-tools](plugins/data-and-ai-tools/README.md) | 3.0.1 | 12 | 12 | Design data, retrieval, AI runtime, model tooling and agent operations. |
  134. | [developer-learning-tools](plugins/developer-learning-tools/README.md) | 3.0.1 | 4 | 4 | Explain technical sources with source-grounded analogies and learner checks. |
  135. | [documentation-tools](plugins/documentation-tools/README.md) | 3.0.1 | 8 | 8 | Refresh, extract, publish and package documentation from real sources. |
  136. | [growth-and-customer-tools](plugins/growth-and-customer-tools/README.md) | 3.0.1 | 15 | 15 | Research buyers, acquire leads, follow up, support customers and grow accounts. |
  137. | [highlevel](plugins/highlevel/README.md) | 3.0.1 | 3 | 3 | Integrate HighLevel, build with AI Studio and map exported workflows. |
  138. | [infrastructure-decision-tools](plugins/infrastructure-decision-tools/README.md) | 3.0.1 | 6 | 6 | Prepare platform assets and account dependencies without implicit setup actions. |
  139. | [littlebird-toolkit](plugins/littlebird-toolkit/README.md) | 3.0.1 | 30 | 0 | Turn Littlebird memory into evidence-backed operating work. |
  140. | [media-and-creative-tools](plugins/media-and-creative-tools/README.md) | 3.0.1 | 4 | 4 | Create consented photography and integrate voice and video production. |
  141. | [platform-and-release-tools](plugins/platform-and-release-tools/README.md) | 3.0.1 | 20 | 20 | Integrate authentication, payments, analytics, messaging and production delivery. |
  142. | [product-studio](plugins/product-studio/README.md) | 3.0.1 | 3 | 3 | Turn an idea into a buildable plan: product strategy, Claude-Design-grade UX, a PRD map, a wave plan and a Definition of Done. |
  143. | [repository-modernization-tools](plugins/repository-modernization-tools/README.md) | 3.0.1 | 1 | 1 | Compose repository baseline, safe refactoring and contributor onboarding through selected specialist owners. |
  144. | [software-economics-tools](plugins/software-economics-tools/README.md) | 3.0.1 | 4 | 4 | Model supplied software economics and costs with explicit scenarios and evidence. |
  145. | [web-development-tools](plugins/web-development-tools/README.md) | 3.0.1 | 30 | 30 | Build web interfaces and sites with React, Svelte, design systems and accessible components. |
  146. | [website-audit-tools](plugins/website-audit-tools/README.md) | 3.0.1 | 21 | 20 | Audit a public website with crawl, SEO, accessibility, conversion and evidence-backed reports. |
  147. The [Claude catalog](.claude-plugin/marketplace.json) and [Codex catalog](.agents/plugins/marketplace.json) expose these packs individually. Runtime guides and research distillations ship with them. Raw research archives, `node_modules/`, and ingested photography models do not. The photography pack retains only its blank model template.
  148. The [complete plugin catalog](learn/reference/PLUGIN-CATALOG.md) lists every shipped Stinger, Drone and command by pack with purposes and direct instructions. The [hook catalog](learn/reference/HOOK-CATALOG.md) covers shared hooks and their host limits.
  149. ## Learn and build on it
  150. - [How We Build](learn/guides/HOW-WE-BUILD.md) ([branded PDF](learn/pdf/How-We-Build-The-Wasp-Nest.pdf)): the whole workflow from idea to shipped, in plain language.
  151. - [Getting Started](learn/guides/GETTING-STARTED.md): install, consent, and first project setup.
  152. - [Components](learn/guides/COMPONENTS.md): Drones, Stingers, commands, rules, and hooks.
  153. - [Write a PRD](learn/guides/WRITE-A-PRD.md), [IRD](learn/guides/WRITE-AN-IRD.md), or [CTR](learn/guides/WRITE-A-CTR.md), then [execute the plan](learn/guides/PRD-EXECUTION.md) with evidence.
  154. - [Document workflows](learn/guides/DOCUMENT-WORKFLOWS.md): Library Packets, App Primer Zero and KB Refresh with example requests.
  155. - [Model Selection](learn/guides/MODEL-SELECTION.md), [Security and Secrets](learn/guides/SECURITY-AND-SECRETS.md), and [Troubleshooting](learn/guides/TROUBLESHOOTING.md).
  156. This repository is generated from canonical source. [Open an issue](https://github.com/legioncodeinc/vibe-coding-tools/issues) for corrections or component requests. Maintainers change the source with Queen Wasp and validate it before release.
  157. ## License and attribution
  158. The Wasp Nest is created by **Mario Aldayuz and [Legion Code Inc.](https://www.legioncodeinc.com)**. First-party material is licensed under [AGPL-3.0-or-later](LICENSE.md). Embedded third-party material retains its own rights; see [third-party notices](THIRD-PARTY-NOTICES.md) and each pack's notices. This license replaces prior repository-specific usage terms.
  159. Built for vibe coders. Go ship something you can prove works.
  160. ---
  161. <div align="center">
  162. <picture>
  163. <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/legioncodeinc/brands/main/legion-code-inc/logos/legion-symbol-dark.svg">
  164. <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/legioncodeinc/brands/main/legion-code-inc/logos/legion-symbol-light.svg">
  165. <img alt="Legion Code Inc. symbol" src="https://raw.githubusercontent.com/legioncodeinc/brands/main/legion-code-inc/logos/legion-symbol-light.svg" width="36">
  166. </picture>
  167. <sub><strong>We are Legion. Vibe with Legion.</strong></sub>
  168. </div>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.