dsh-codex-harness

Automated evidence available

Compact Codex coding mode for DSH: light prompt guardrails against GPT over-explaining, with an editable prompt and native Codex-style tools.

Author: shuind · Models & Providers · Catalog snapshot: 2026-09-19

Canonical semantic path

Development & CodeCoding Workflow & Behavior GovernanceAgent Presets, Context & Project Onboarding

One primary path; alternate capabilities remain separate.

What it may solve

Compact Codex coding mode for DSH: light prompt guardrails against GPT over-explaining, with an editable prompt and native Codex-style tools.

Imported third-party catalog description; not a Registry verification conclusion.

Sources and public signals

shuind/dsh-codex-harness

6 stars · 7943 downloads

Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19

What can currently be confirmed

Active analysis coverage 1/5. Historical chains are retained but do not count toward current coverage.

Not analyzed

Source structure

Source structure has not been analyzed.

Not analyzed

Repository health

Repository metadata has not been analyzed.

Not analyzed

npm release

npm release metadata has not been analyzed.

Not analyzed

DSH compatibility

Installation and startup verification has not been run.

Not analyzed

Dependency audit

Dependency audit has not been run.

Not analyzed

Functional verification

The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.

Analysis failed

Static risk scan

Conclusion: The static risk scan could not complete because package validation did not pass.

Analysis complete

Package integrity

Conclusion: Core package structure passed, but an optional export path is missing.

Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.

Continue with the latest plugin manager

Describe your task in a DSH conversation and mention dsh-codex-harness. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.

Install or update the plugin manager (latest)