Caxson

9 mods across 1 repository, 2 stars between them.

proof-of-work

01

Caxson/proof-of-work

Plugin Claude Code

Engineering-discipline layer for Claude Code — evidence-first doctrine and verification skills that make the agent prove its work.

2 3mo ago A tokens not measured original Apache-2.0

proof-of-work

02

Caxson/proof-of-work

Plugin Claude Code

An engineering-discipline layer for Claude Code: an evidence-first doctrine injected every session, plus verified-delivery and evidence-first-debugging skills. Makes the agent prove its work instead of claiming success.

2 3mo ago A tokens not measured original Apache-2.0

Caxson/proof-of-work

Instructions file CodexOpenCode

Instructions for Caxson/proof-of-work, a project described as: A disciplined-engineer + persistent-self layer for Claude Code.

2 3mo ago A 3 tokens copy · 77% Apache-2.0

diagnose

04

Caxson/proof-of-work

Command

Evidence-first diagnosis of a bug/failure ($ARGUMENTS).

2 3mo ago A 13 tokens original Apache-2.0

doctrine

05

Caxson/proof-of-work

Command

Re-surface the proof-of-work Engineering Doctrine and treat it as binding for the rest of this session.

2 3mo ago A 21 tokens original Apache-2.0

verify

06

Caxson/proof-of-work

Command

Run the verified-delivery workflow on the current task (or $ARGUMENTS).

2 3mo ago A 17 tokens original Apache-2.0

SessionStart

07

Caxson/proof-of-work

Hook

Runs when a session starts on startup, clear and compact, executing run-hook.sh. From Caxson/proof-of-work.

2 3mo ago A tokens not measured original Apache-2.0

Caxson/proof-of-work

Skill Claude CodeCodex

Use when diagnosing a failure, bug, freeze, crash, or any "why doesn't this work" — gather concrete evidence (logs, real data, a reproduction) BEFORE naming a root cause, rule out your own code first, rank hypotheses by confidence with the supporting evidence attached, and fix the root cause rather than the symptom…

2 3mo ago A 77 tokens original Apache-2.0

verified-delivery

09

Caxson/proof-of-work

Skill Claude CodeCodex

Use when building, fixing, or implementing anything that can be run — decompose the work into steps, prove EACH step with real actions (Playwright screenshots, SQL/database checks, API round-trips, device screenshots) against real data, never mock data, and refuse to mark the task done until you have an evidence…

2 3mo ago A 74 tokens original Apache-2.0