Add dsh-product-subagent-console

[Jokasa7]

Summary

Add dsh-product-subagent-console to the DeepSeek Harness Plugins section in alphabetical order.

The plugin designs multi-Agent plans, observes real child-session trees, compares approved tasks with runtime attempts, and prepares evidence-backed recovery inside DSH conversations.

Verification

• Public source: https://github.com/Jokasa7/dsh-product-subagent-console
• Current release: https://github.com/Jokasa7/dsh-product-subagent-console/releases/tag/v0.9.0
• package.json declares dsh.bundle
• The root plugin exports a valid Cordis Service class entry point; supporting tool and client modules expose Cordis apply functions
• README documents the tested dsh plugin add release-package flow
• v0.9.0 release checks: https://github.com/Jokasa7/dsh-product-subagent-console/actions/runs/33244167092

[github-actions]

✅ Contribution check passed. @Jokasa7, catalog validation succeeded.

scan findings

HOL centralized scan reported findings or did not pass: failure. This is advisory and does not block listing.

Recommended: add scanner CI for security

This listing can merge without it. HOL still scans Jokasa7/dsh-product-subagent-console independently.

We recommend including hashgraph-online/ai-plugin-scanner-action under .github/workflows/ on push and pull_request. Continuous scanning keeps this catalog safer for MCP servers, skills, plugins, and other agent extensions people install from HOL.

Adding it:

• protects the ecosystem by catching secrets, dangerous hooks, and supply-chain issues before they ship;
• keeps the listing at the full trust score (without maintainer CI it stays eligible, with a 10% trust-score reduction);
• can surface findings in GitHub code scanning.

See CONTRIBUTING.md and SCANNER_GUIDE.md.

HOL's centralized scan reported findings. This does not block listing.

View the latest sweep.

[Jokasa7]

For reviewer context, I reproduced the advisory scanner result from the catalog workflow:

• The three high findings are literal fixtures used by redaction/rejection tests (tests/recipe.spec.ts, tests/capsule.spec.ts) plus a no-network smoke placeholder in scripts/smoke-clean-profile.mjs; none is a live credential. GitHub secret scanning reports no open alert.
• The three medium findings come from scanner 2.0.1116 falling back to the Codex plugin adapter and requiring .codex-plugin/plugin.json. This repository is a DSH Cordis plugin, so adding a fake Codex manifest would be incorrect.
• The Dependabot warning is a real low-severity maintenance improvement and can be handled separately.

I have left the source format unchanged and am treating the scan as the advisory signal described by this catalog, not as a safety guarantee.

[github-actions]

🎉 Hey @Jokasa7, your plugin has been merged and is now listed in the HOL Registry!

Claim your plugin

As the author, you can verify ownership of your plugin to unlock:

• Owner-verified badge on your plugin's registry listing
• Trust score visibility and analytics for your plugin
• Direct claim link to share with your community
• Dashboard access at hol.org/guard/plugins to track installs, trust, and engagement

How to claim

1. Visit hol.org/guard/plugins
2. Find your plugin and click "Verify ownership"
3. Sign in with GitHub — we only request read:user, user:email, and read:org (no write access to your repos)
4. We verify you own the repository, and your plugin gets the ✅ owner-verified badge

The whole process takes under 30 seconds. No need to add any secrets or tokens to your repo — verification is done entirely through GitHub OAuth.

If you have any questions, feel free to ask here or reach out at support@hol.org.

[kantorcodes]

Hi @Jokasa7 — a quick follow-up about your plugin jokasa7/dsh-product-subagent-console.

The listing is live in the HOL Registry, and ownership verification is still available at HOL Guard.

Verifying ownership takes about 30 seconds and unlocks the owner-verified badge, plugin analytics, and the author dashboard. Sign in with GitHub; no repository write access is needed.

We may follow up again later if ownership verification is still incomplete.

If you already completed verification, no action is needed — the next scheduler run will stop these reminders.

[kantorcodes]

Hi @Jokasa7 — a quick follow-up about your plugin jokasa7/dsh-product-subagent-console.

The listing is live in the HOL Registry, and ownership verification is still available at HOL Guard.

Verify ownership with the GitHub account that owns the repository to unlock the owner-verified badge, plugin analytics, and the author dashboard. No repository write access is needed.

We may follow up again later if ownership verification is still incomplete.

If you already completed verification, no action is needed — the next scheduler run will stop these reminders.