DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to pull the catalog index to audit plugin counts and rejections with DSH Plugin Shop

Read the published index.json and its data files to review what the catalog lists and rejects.

Who it is forA researcher or maintainer who wants a snapshot of the DSH plugin ecosystem without browsing the shop.

The problemThe shop UI does not show download counts or reviews, so a structured view of listed and rejected plugins takes manual effort.

The outcomeA summary of the listed count, the rejected total, the build time, and the plugins in each category.

What you need first

  • Node.js installed, with npm available
  • DeepSeek Harness (dsh) installed globally with npm install -g @deepseek-ai/dsh pnpm, or run through npx
  • A dsh profile name to use (the README uses web as the example)
  • Willingness to trust installed plugins, since they have full access to ctx including the filesystem and shell

Steps

  1. Fetch the index with curl -s https://LivXue.github.io/dsh-plugin-shop/v1/index.json. (inferred, check the README)
  2. Read the count, rejected, and builtAt fields from the response.
  3. Use the content hashes in the index to fetch the matching plugins.<hash>.json data file.
  4. If a data URL returns 404, fetch index.json again, because it is cached for ten minutes.

Prompt for your agent

Fetch https://LivXue.github.io/dsh-plugin-shop/v1/index.json and report the schemaVersion, builtAt, count, and rejected fields. Then fetch one plugins data file named in the index and confirm it parses as JSON.

Caveat. The README says each source serves identical data, so a cached or stale index may point to files that no longer exist, and the fetched numbers may differ from the current build.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page