DCS
Drunken Coding Skills: a deliberately small, personal library of the Agent Skills I actually use.
The repository root is a skill-only Agent Plugins 1.0
package. Its root plugin.json declares the portable format, and clients discover
skills from skills/ by convention. There is intentionally no legacy client-specific plugin
manifest.
The package contains three maintainer-owned skills:
file-propens a focused pull request for the current branch.babysit-prmonitors an existing pull request through reviews and CI.ask-opusgets a second opinion from Opus throughclaude -p.
It also tracks selected public skills:
anti-ui-slophelps agents build product-specific interfaces and check them for generic UI defaults.deslopremoves AI-generated code slop. DCS tracks the skill from Cursor's publiccursor/pluginsrepository.pstackprovides one explicit, evidence-first engineering workflow distilled from Lauren Tan's pstack principles, quality rubric, and core playbooks.thermo-nuclear-reviewperforms a strict correctness and security branch audit.thermo-nuclear-code-quality-reviewperforms a strict maintainability and structure audit.thermosruns both Thermo-Nuclear reviews concurrently and synthesizes the results.
Future skills belong in skills/ and should be added only when they earn their place.
Upstream skills
upstreams.json is the complete administration file for third-party skills. Each entry names a public Git repository, a ref, the source directory, and its destination under skills/.
Most skills are exact mirrors. Adapted skills can also name a small adapter, patch, or file overlay under ports/. The pstack adapter tracks the complete upstream plugin but packages one Codex-native pstack skill instead of its Cursor-specific skill stack, agents, model router, and automations. It verifies pstack's identity and main router before packaging the port. The Thermos ports remove Cursor-only invocation metadata, replace Cursor's subagent syntax with Codex instructions, and add Codex UI metadata. upstreams.lock.json records each adapted upstream Git tree, so a change remains visible even when an adapter produces identical packaged output. Its managedSkills list tracks every generated skill so removing a registry entry also removes its packaged directory.
Install the synchronizer's YAML dependency once:
python3 -m pip install -r tools/requirements.txt
Check for upstream changes without modifying the repository:
python3 tools/sync_upstreams.py --check
Synchronize registered skills locally:
python3 tools/sync_upstreams.py --sync
The Upstream skills GitHub Actions workflow runs the check every night. A changed upstream makes the run fail so normal GitHub Actions notifications can alert you. Its manual sync operation imports exact upstream directory contents, bumps the DCS patch version, pushes a dedicated update branch, and puts a one-click pull request link in the run summary. It never changes main or merges anything.
The workflow uses only the repository's built-in GITHUB_TOKEN. It needs no personal access token, AI API key, or other secret.
Install
The portable specification leaves installation and distribution to each client. DCS keeps
.agents/plugins/marketplace.json only as its Codex distribution index; it is not part of the
plugin package format.
Portable Agent Plugins installation requires Codex 0.147.0 or later. Add this repository as a marketplace, then install and enable DCS:
codex plugin marketplace add the-Drunken-coder/DCS --ref main
codex plugin add dcs@dcs
Verify the installation:
codex plugin list --marketplace dcs
Update
Refresh the marketplace snapshot and reinstall DCS:
codex plugin marketplace upgrade dcs
codex plugin add dcs@dcs
Disable or remove
To disable DCS without uninstalling it, open DCS in the Codex Plugins Directory and turn it off. The current CLI has no plugin-disable subcommand.
To uninstall DCS while keeping its marketplace configured:
codex plugin remove dcs@dcs
To also remove the marketplace:
codex plugin marketplace remove dcs
Local development
Clone and validate the plugin:
git clone https://github.com/the-Drunken-coder/DCS.git
cd DCS
python3 -m unittest discover -s tests -v
python3 tools/sync_upstreams.py --validate
python3 tools/sync_upstreams.py --check
The repository validator also enforces DCS release policy: a plain Semantic Versioning release, a non-empty description, and a named author. Those requirements are intentionally stricter than the minimum portable manifest schema.
To test the checkout directly, replace only the DCS marketplace with the local repository and reinstall:
codex plugin remove dcs@dcs
codex plugin marketplace remove dcs
codex plugin marketplace add "$PWD"
codex plugin add dcs@dcs