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

How to install the jev plugin into DeepSeek Harness from a checkout with Jevcore

Add the jevcore-dsh package and its core dependency to a DSH profile and confirm it is active.

Who it is forA DeepSeek Harness user who wants Jev judgments available to the model and to other plugins.

The problemThe plugin needs its core package resolvable from the profile, and a failed load is easy to miss.

The outcomeThe jev plugin shows as active in the plugin list, and the startup log shows the egress contract for the mock provider.

What you need first

  • Node 20 or later for jevcore and jevcore-mcp, or Node ^22.19.0 or >=24.0.0 for jevcore-dsh
  • A local checkout of the repo for the DeepSeek Harness install path
  • DeepSeek Harness, if you use the plugin or the gates
  • A TypeSafe or OpenRouter key only if you choose a live route; the default is the offline mock

Steps

  1. Clone the repository with git clone https://github.com/PerryLink/jevcore and note the absolute path of the checkout. (inferred, check the README)
  2. Run dsh plugin --profile add /absolute/path/to/jevcore/packages/dsh, replacing the path with your checkout.
  3. Run dsh plugin --profile add /absolute/path/to/jevcore/packages/core so the core package resolves from the profile. (inferred, check the README)
  4. Confirm the jev row shows as active, not failed, in the plugin list.
  5. Open the log and check the startup line that reads provider=mock and egress=OFF.

Prompt for your agent

Using the PerryLink/jevcore checkout at <absolute path>, add packages/dsh and packages/core to the DeepSeek Harness profile with the dsh plugin command. Expected output: the jev plugin listed as active. Verify that the log contains provider=mock and egress=OFF before reporting success.

Caveat. The README says the dsh package needs Node ^22.19.0 or >=24.0.0, so an older runtime will fail to load the plugin even when the install command succeeds.

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