← Plugin catalog
Developer Tools

Qodo

Qodo v2.1.11

Code intelligence and review

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Set up Qodo
  • Qodo Codebase Wisdom
  • Qodo Local Review

Not specified in the available declarations: limitations, pricing & account requirements.

Onboarding example

Use $qodo-codebase-wisdom to explain how this code works and cite the evidence.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 16, 2026. Package observed Nov 15, 2026.

View package source →

Description

From the marketplace listing

Qodo setup, code intelligence, and review workflows.

Language: English · Automatically detected from descriptions.

Matches for “agent code”

Exact text from the indicated source. A mention alone does not establish support for your task.

Publisher keywords · listing

qodo code-review code-intelligence standards coding-agents

Publisher subtitle

Code intelligence and review

Publisher capabilities · listing

Set up Qodo Qodo Codebase Wisdom Qodo Local Review Qodo Review Notes Qodo Review Resolver

Publisher description

Qodo setup, code intelligence, and review workflows.

What changed

· 8 observations

Capabilities & instructions

Supporting files updated; open the comparison for details. Skill instructions changed from “"1.0.12" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" --- # Set up Qodo ## Description Verify the available...” to “"1.0.14" recommended: "true" package: "qodo" distribution:...

View comparison →
Capabilities & instructions

Skill instructions changed from “"1.4.9" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" arguments: - name: autofix description: Optional...” to “"1.4.10" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" arguments: - name:...

View comparison →
Capabilities & instructions

Full description changed from “Find and maintain Development Track Notes and PR Review Notes through Qodo tools. Use at task intake or when resuming a development effort, before opening a...” to “Preserve reasoning for independent review of plans and PRs through Qodo notes tools. Use during substantive planning and...

View comparison →
Capabilities & instructions

Supporting files updated; open the comparison for details. Skill instructions changed from “"1.10.11" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" --- # Local Review ## Description Review **local...” to “"1.10.15" recommended: "true" package: "qodo" distribution:...

View comparison →
Capabilities & instructions

Skill instructions changed from “"1.1.7" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" --- # Codebase Wisdom ## Description Use Qodo managed...” to “"1.1.8" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" --- # Codebase...

View comparison →
Capabilities & instructions

Skill “qodo-review-notes” description changed from “Find and maintain Development Track Notes and PR Review Notes through Qodo tools. Use at task intake or when resuming a development effort, before opening a...” to “Preserve reasoning for independent review of plans and PRs through Qodo notes tools. Use during...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

· 5 observations

Capabilities & instructions

Supporting files updated; open the comparison for details. Skill instructions changed from “"1.0.11" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" --- # Set up Qodo ## Description Verify the available...” to “"1.0.12" recommended: "true" package: "qodo" distribution:...

View comparison →
Capabilities & instructions

Supporting files updated; open the comparison for details. Skill instructions changed from “"1.10.10" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" --- # Local Review ## Description Review **local...” to “"1.10.11" recommended: "true" package: "qodo" distribution:...

View comparison →

Technical updates · 2

Package or technical metadata updated

View technical comparison →

Package or technical metadata updated

View technical comparison →

· 7 observations

Capabilities & instructions

Supporting files updated; open the comparison for details. Skill instructions changed from “"1.0.9" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" --- # Set up Qodo ## Description Install, connect and...” to “"1.0.11" recommended: "true" package: "qodo" distribution:...

View comparison →
Capabilities & instructions

Full description changed from “with the qodo” to “using Qodo managed tools through MCP or the”. Supporting files updated; open the comparison for details. Skill instructions changed from “with the qodo CLI — fetch structured status, reviewed commit SHA, and findings for ANY PR as JSON, with optional extended details...

View comparison →
Capabilities & instructions

Supporting files updated; open the comparison for details. Skill instructions changed from “"1.10.7" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" --- # Local Review ## Description Use the `qodo` CLI to...” to “"1.10.10" recommended: "true" package: "qodo" distribution:...

View comparison →
Capabilities & instructions

Full description changed from “the qodo CLI's managed tools.” to “Qodo managed tools through MCP or the CLI.”. Supporting files updated; open the comparison for details. Skill instructions changed from “the qodo CLI's managed tools. Use when a task needs to understand a codebase, its history, or how its repos relate...

View comparison →
Capabilities & instructions

Capabilities updated; open the comparison for details. Declared skill added: “qodo-review-notes”. Skill “qodo-codebase-wisdom” description changed from “the qodo CLI's managed tools.” to “Qodo managed tools through MCP or the CLI.”. Skill “qodo-review-resolver” description changed from “with the qodo” to “using Qodo...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

· 7 observations

Capabilities & instructions

Skill instructions changed from “"1.0.8" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" --- # Set up Qodo ## Description Install, connect and...” to “"1.0.9" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" --- # Set up Qodo ##...

View comparison →
Capabilities & instructions

Skill instructions changed from “"1.4.6" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" arguments: - name: autofix description: Resolve the...” to “"1.4.7" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" arguments: - name:...

View comparison →
Capabilities & instructions

Supporting files updated; open the comparison for details. Skill instructions changed from “"1.10.5" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" --- # Local Review ## Description Use the `qodo` CLI to...” to “"1.10.7" recommended: "true" package: "qodo" distribution:...

View comparison →
Capabilities & instructions

Skill instructions changed from “"1.1.4" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" --- # Codebase Wisdom ## Description Use the `qodo` CLI...” to “"1.1.5" recommended: "true" package: "qodo" distribution: "marketplace" instruction_mode: "embedded" --- # Codebase...

View comparison →

Technical updates · 2

Package or technical metadata updated

View technical comparison →

Package or technical metadata updated

View technical comparison →

Keywords

Files & skills

File archives

Plugin package32 files · 81.3 KBBrowse files →
Skill instructions
qodo-codebase-wisdom15.4 KB

View saved version →

---
name: qodo-codebase-wisdom
description: Understand how code works, how a change was done before, and which repos are coupled — to answer a question, plan a code change, debug a regression, or scope a fix, using Qodo managed tools through MCP or the CLI. Use when a task needs to understand a codebase, its history, or how its repos relate — especially for a repo you don't have checked out or work spanning repos — "how does X work", "where is X defined", "who changed X", "explain this service", "plan the change for X", "what would changing X affect", "which repos depend on X", "why did X regress / when did it break", "has this been fixed before", "how did we solve X".
owner: Qodo
metadata:
  vendor: qodo
  version: "1.1.8"
  recommended: "true"
  package: "qodo"
  distribution: "marketplace"
  instruction_mode: "embedded"
---

# Codebase Wisdom

## Description

Use Qodo managed tools to learn how code works, how a change was done before, and how repos
are coupled — then hand back **cited findings**. This feeds answering a question, planning
a change, debugging a regression, or scoping a fix. It reaches repos you don't have on disk
and spans repo boundaries. You drive qodo's **read** tools only; you never post to the forge.

## Prerequisites

- The required tools are available through a connected QAR managed-tools MCP server or the Qodo CLI.
- The workspace exposes the required read-only Codebase, pull-request, or cross-repo tools.
- The current provider-owned Qodo skill package is loaded in this agent session.

## Instructions

### Choose the execution path

Use the host's connected QAR managed-tools MCP tools when the required read capability is
available; otherwise use the CLI instructions below. Do not require a CLI version probe,
`qodo login`, or a CLI catalog refresh on the MCP path. A connected MCP server has already
handled transport authentication; a missing tool or `MT-AUTH-FORBIDDEN` is a capability or
authorization failure, not a reason to log in through the CLI. Do not silently switch paths
after an auth or permission denial.

On MCP, use the tool descriptions, `inputSchema`, and `readOnlyHint` supplied by the host.
Call only read-only tools. Representative wire names are `litegit-search-repos`,
`litegit-grep`, `litegit-read-file`, `pull-request-similar`, and
`cross-repo-relations`; resolve the actual names and arguments from the connected catalog.
Pass explicit `repo` when needed: MCP does not infer the local Git origin like the CLI.
Check `isError` before using `structuredContent`; preserve typed errors and incomplete or
truncated results. If a call becomes an MCP Task, collect its terminal result before drawing
a conclusion. A missing MCP capability may use an already authorized CLI path for the same
deployment; do not treat different accounts or tenants as interchangeable.

The version, identity, help, command, and refresh steps below apply only to the CLI path.

At investigation start and when moving into implementation, identify the missing context:

- Use Qodo to discover unfamiliar code, prior solutions, historical rationale, and relationships
  across repositories, even when the repositories are available locally.
- Use local tools for exact branch/worktree state, uncommitted changes, edits, and tests.
- Reuse an earlier investigation when it covers the current scope and revisions. Briefly name
  the evidence being reused; refresh the relevant context when scope, dependencies, or evidence
  changes. Do not repeat remote reads solely to demonstrate skill use.

When context is missing, resolve a concrete question through the appropriate tool group below. Connect
retrieved evidence to the answer or implementation decision. Version, identity, and catalog
checks establish readiness; they are not codebase context retrieval.

## Handle a skill update notice

Treat `QODO_NOTICE` updates as passive, even if an older CLI requests action. Continue the task
without inventory or update questions; mention each event at

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 4 — file references are metadata, not package contents.

qodo-review38.2 KB

View saved version →

---
name: qodo-review
description: Review local changes with Qodo during substantive coding milestones and before a PR or completed-work handoff. Use light background checkpoints while coding, collect and assess findings with session context, and run a final review before handing off. Also use for "review my local diff", "pre-PR review", or "run qodo review". Use qodo-review-resolver for findings already posted on a PR.
owner: Qodo
metadata:
  vendor: qodo
  version: "1.10.15"
  recommended: "true"
  package: "qodo"
  distribution: "marketplace"
  instruction_mode: "embedded"
---

# Local Review

## Description

Review **local changes during coding and before handing off completed work**. `qodo review` sends your diff, new/untracked files and coding-session context to Qodo. Evaluate its structured findings and apply authorized fixes. Only the base commit must be on the remote; the command never pushes or creates a PR.

Use this skill for local changes, including unpushed work on an existing PR. Use `qodo-review-resolver` to work on findings from the PR's remote review; do not duplicate that review for an unchanged pushed snapshot.

## Prerequisites

- An authenticated Qodo CLI is available, or a connected QAR MCP server and a tested local input collector are available; review capability is enabled.
- The comparison base exists on the remote; local changes and context need not be pushed.
- The coding-session context and any ticket or design references are ready to attach.

## Choose when and how deeply to review

| Situation | Selection |
|---|---|
| A coherent milestone during substantive coding | `--fast --async`: light checkpoint; continue useful coding and collect the result. |
| Ordinary final review before opening/updating a PR or handing off completed work | Omit both depth flags: auto. Collect and assess the result before claiming review completion. |
| User intent calls for unusually thorough scrutiny, or a known high blast radius warrants it | `--deep`, with a brief reason tied to the request or affected behavior. |

Automatic coding checkpoints always use `--fast`. A deliberate deep review can happen earlier when
one of the exceptions above applies. A request such as "examine subtle races thoroughly" can justify
it without the word "deep"; generic "review" or "double-check" does not. Identify concrete impact,
such as shared authorization, a destructive migration, or a contract used by multiple services.
Diff size, session length, PR readiness, or a security-related filename alone do not justify deep.

With **no flag**, the CLI omits depth and the reviewer/deployment selects it. Auto can select deep;
it is not guaranteed standard and does not impose a spending cap. There is no `--standard` flag.
`--fast` and `--deep` are mutually exclusive; depth is selected anew for each invocation.

## Checkpoints and final handoff

- Review a completed, testable slice when its feedback can guide the remaining work. Do not review
  unfinished exploration, every edit, trivial changes automatically, or simply because time passed.
  Respect the user's review scope and budget. A pause for a question or approval is not a final handoff.
- Keep at most one automatic checkpoint active per task. Retain its operation ID, submitted scope
  and snapshot/context association in the task's existing state. Poll status at natural pauses while
  doing useful work; do not launch another review to check progress or re-review unchanged inputs.
- Collect every submitted result within its retention window. Recheck findings against current code
  before acting: the working tree may have changed. A superseded result cannot certify newer work.
  Use the existing CLI lifecycle; no separate sub-agent or scheduler is required.
- Before final review, collect the outstanding checkpoint and reconcile its findings. Review the
  full intended change with auto, or justified deep, rather than handing off on a light checkpoint.
  Remove temporary path restrictions that

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 9 — file references are metadata, not package contents.

qodo-review-notes30.8 KB

View saved version →

---
name: qodo-review-notes
description: Preserve reasoning for independent review of plans and PRs through Qodo notes tools. Use during substantive planning and development, when decisions, scope or validation change, when resuming or handing off work, and before opening or updating a PR. Tracks hold the evolving plan across issues and repositories; PR notes explain one change. Also use to read or maintain reviewer context. This skill does not review or approve a plan or code, implement it, or open a PR.
owner: Qodo
metadata:
  vendor: qodo
  version: "1.0.4"
  recommended: "true"
  package: "qodo"
  distribution: "marketplace"
  instruction_mode: "embedded"
---

# Development Tracks and PR Review Notes

## Description

A diff shows the change; the author also knows the problem, constraints and reasons behind it.
Preserve that context so an independent reviewer can challenge a plan before implementation and
assess the resulting PR, and another coding session can continue without reconstructing the chat.
Development Track Notes hold the evolving plan across issues, repositories and PRs. PR Review
Notes explain one change and link to a track explicitly. Judge usefulness by the review questions
the notes help answer, rather than their length or number of saves.

## Capture reasoning as work develops

For substantive work with existing notes-maintenance authority, maintain notes as part of the
task without repeated permission questions. A request to read or review alone is not write
authority; preserve a drafts-only instruction and the host's actual write/publication gates.

Read relevant notes at intake or resume. Save meaningful new context when:

- A plan has concrete goals, constraints, proposals or decisions worth reviewing, before coding.
- The chosen approach, scope, assumptions, dependencies or a significant risk changes.
- Verification changes what is known, fails, or leaves an important path untested.
- Work is handed off or paused with new context; a PR is opened or updated with changed work.

Use the track for early plan context; no PR, source commit or implementation is needed to save
a track. A plan-only task stays plan-only. Avoid placeholder records at intake, a track for every
tiny edit, and unchanged saves on every turn. A small independent fix can have PR notes alone.
When nothing relevant changed, reuse the existing revision.

For a reviewable plan, capture the intended outcome, constraints and non-goals; the proposed
approach and its reasons; meaningful alternatives actually considered; assumptions and risks;
dependencies/order; and how the plan will be checked, including unresolved questions for the
reviewer. Scale this to the task instead of filling empty headings. Clearly separate proposals,
user-selected decisions and coding-agent choices, with known rationale. Leave unknown ownership
or rationale explicit. A proposal in notes is neither approval nor authority to implement it.
Keep planned checks separate from completed results; never invent a choice, test or business case.

Keep a concise current summary first. Incorporate new facts into the present account and replace
superseded status text, preserving useful rationale, constraints and other authors' contributions.
Use saved revision history for chronology instead of appending old summaries into the current
body. Resolve conflicts in evidence explicitly; do not silently erase a still-relevant disagreement.
Shared goals and delivery order belong in the track. Each PR note should explain that PR's distinct
behavior, decisions and review risks instead of copying the whole track into every PR.

## Prerequisites

Use an authenticated Qodo connection to the intended deployment and workspace. Notes tools must
be available in the live catalog. For CLI use, require Qodo CLI **2.0.0 or newer** and the
PR commands' `localGitCapture` capability. A trusted MCP connection can supply the same operations.

## Instructions

Discover the tools, select the track explicitl

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.

qodo-review-resolver32.2 KB

View saved version →

---
name: qodo-review-resolver
description: Read or resolve a pull request's Qodo review using Qodo managed tools through MCP or the CLI — fetch structured status, reviewed commit SHA, and findings for ANY PR as JSON, with optional extended details and citation evidence for audits, then optionally resolve open findings and record outcomes, once or until clean. Use this — never `gh`/`curl` scraping of review comments — for "is the review clean on PR #N", "get Qodo's findings for <pr> as JSON", "audit the review evidence", "show finding citations", "what did Qodo flag", "is this review up to date with head", "check before merging", "resolve my PR review", "fix the review findings", or "babysit this PR until it's clean".
triggers:
  - "Check the Qodo findings on this pull request"
  - "Audit the citation evidence for these Qodo PR findings"
  - "Resolve the open Qodo review findings on this PR"
owner: Qodo
when_to_use: When you need to read or act on a pull request's Qodo review — check where it stands, see what it flagged, gate a merge on it being clean at head, or fix the open findings — for any PR, not just your own. It reads the review through qodo's managed tool (structured, git-provider-agnostic), so use it instead of scraping the rendered PR review comments with `gh`/`curl` (lossy, provider-specific, and easy to read stale against the head commit). It resolves findings in local code and then records the outcome on each finding through qodo's own tools (dismiss / mark-implemented, which clear the merge-policy block); it never posts to the git forge itself. Skip it for reviewing code you're writing locally before any PR exists (that's the pre-PR review), and for non-review PR chores (merging, labels, descriptions).
metadata:
  vendor: qodo
  version: "1.4.10"
  recommended: "true"
  package: "qodo"
  distribution: "marketplace"
  instruction_mode: "embedded"
arguments:
  - name: autofix
    description: Optional shorthand for authorizing supported fixes. An explicit fix request or covering implementation authority also permits those fixes without another prompt.
    optional: true
---

# Read & Resolve Findings

## Description

Use Qodo managed tools to read a pull request's **review session** — its status, the commit that
was reviewed, and every finding with its resolution status — for **any** PR (yours or someone
else's). Request extended results when auditing citations or investigating a finding's supporting
evidence, location, dismissal, or review-run history. Reading alone is a valid use: stop after the read to report where a review stands or
what it flagged (e.g. to gate a merge on it being clean at head). To go further, **resolve the
open findings in code**, applying your own judgment (the review is a strong second opinion, not
gospel). Apply supported fixes when the user has authorized them; otherwise present your assessment
for selection. Run once (report + authorized fixes) or as a watch loop (resolve →
let Qodo re-review the new commit → repeat until clean). When separately authorized, **record the outcome** on the findings
you settled — `mark-implemented` for ones you fixed, `dismiss` for ones the user agreed to close
without a code change. That is what clears the merge-policy block those findings hold; skip it and
the review stays red until a human clicks through the PR. You still never post to the forge
yourself: the status tools write Qodo's review DB and Qodo reconciles the PR comments. (Plain
git/forge *metadata* reads — `git rev-parse HEAD`, `gh pr view --json headRefOid` — are fine and in
fact required for the freshness check below; the "don't scrape" rule is about qodo, not your shell.)

## Prerequisites

- A connected QAR managed-tools MCP server or authenticated Qodo CLI exposes review-session tools.
- The exact PR URL and its current head SHA can be resolved without scraping review comments.
- Any finding-status write has explicit user authorization; code-fix authority or `autofix` alone does not cover

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 4 — file references are metadata, not package contents.

qodo-setup3.86 KB

View saved version →

---
name: qodo-setup
description: Set up Qodo in a coding agent — install the CLI, sign in, and verify tools. Use after plugin installation, on setup requests, or when a Qodo skill finds a missing CLI or login.
owner: Qodo
metadata:
  vendor: qodo
  version: "1.0.14"
  recommended: "true"
  package: "qodo"
  distribution: "marketplace"
  instruction_mode: "embedded"
---

# Set up Qodo

## Description

Skill installation is not readiness. References are relative to this SKILL.md.

## Prerequisites

Shell or host-connected QAR MCP; never handle credentials.

## Instructions

### Connected MCP

Inspect QAR schemas; call a harmless read and check isError before structuredContent. A catalog proves neither read nor write access; never test-write. Host/QAR own auth. Report missing tools, MT-AUTH-FORBIDDEN or connection errors; never request API keys. For MCP-only setup, hand back. CLI collection uses the same deployment.

### Runtime

PowerShell: resolve the verified native/Node invocation in [runtime.md](references/runtime.md). POSIX: probe:

```sh
qodo --version
```

Then try `"${QODO_HOME:-$HOME/.qodo}/bin/qodo" --version` if missing. Use that verified installer if missing. Setup covers installation subject to host approvals; plugin installation alone does not.
Keep the executable as `<qodo>`. Require Qodo CLI **2.0.0 or newer** before auth; compatible versions skip update preflight.

### Runtime compatibility recovery

For old/unparseable versions, stop authenticated calls and explain. Before update checks/changes, test only whether QODO_UPDATE_BASE_URL is set; never print/change it. If set, stop for user resolution. All routes preserve origin, exact versions and update holds; never replace an exact version with a channel.
For parsed1.x, normal `qodo update` reaches approved stable2.x only if that origin enables migration. Require a newer compatible same-origin2.x target from the selected route's supported check. If legacy aliases serve1.x, check latest-2 before proposing `qodo update --channel latest-2`. Missing/failed checks stop; never assume activation or unrelated future-major authority.
For unparseable version/no supported updater, use the checksum-pinned installer reference. Preserve supported customer selectors/settings; normal verified installation selects the approved version. Explain the route; reuse covering runtime/installation authority or ask once before changing it. Make one approved attempt, reprobe unadorned version, and stop on denial/failure/incompatibility without another route, skill edits or an auth diagnosis.

### Connect and verify

Run:

```sh
<qodo> read whoami --json --skill qodo-setup --skill-version 1.0.14 --distribution marketplace --host codex
```

Reuse success. Read [authentication.md](references/authentication.md) before login on failure; preserve deployment, never fall back to Cloud. Wait/recheck identity; stop on denial/cancellation. Diagnostic approval is not blanket authority.
Only after identity succeeds run:

```sh
<qodo> tools --refresh --json --skill qodo-setup --skill-version 1.0.14 --distribution marketplace --host codex
```

Require task capability. On failure report signed in but tools unavailable, exact error and that retry; do not log in again. Reuse verified context with host approvals.

## Configuration

Setup does not authorize enterprise installation/maintenance. Disclose packages/maintenance; preserve opt-outs, edits, owners and choices. Never install optional Standards. For QODO_NOTICE/repeated Kiro read approvals read [host-recovery.md](references/host-recovery.md). CLI owns credentials/transport/updates; lifecycle owners update skills.
## Error Handling

Report the error and one next action. Never claim readiness after failure, disable Keychain, copy credentials, change permissions or offer unrestricted approvals.

## 4. Hand off

Confirm Qodo connection/tools and return to the task. Readiness does not guarantee later access.

Referenced files: 5 — file references are metadata, not package contents.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
MIT
Package author
Qodo
Keywords
See keywords

Declared capabilities

  • Set up Qodo
  • Qodo Codebase Wisdom
  • Qodo Local Review
  • Qodo Review Notes
  • Qodo Review Resolver

Package observed Nov 15, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 16, 2026 · 06:00 UTC
Latest observed change
Nov 9, 2026 · 12:07 UTC
Collection status
Collected

plugins_6a9cec4a630481918ae67f99e032e4d7

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.