Files
Seth Hobson d31e8b8fea fix: address PR review + upgrade ruff/ty so CI matches local
Review feedback:
- codex.py: Codex marketplace entries now conform to the openai/codex
  core-plugins schema — source {source: "local", path}, policy
  {installation, authentication}, and category (was missing required
  fields; flagged P1). Top-level trimmed to {name, plugins}.
- codex.py: interface.shortDescription cuts on a word boundary + ellipsis
  instead of a mid-word [:120] slice in committed .codex-plugin manifests.
- cursor.py: top-level .cursor-plugin/plugin.json displayName is now the
  short "Claude Code Workflows" instead of the long marketplace description.

Tooling (local drives CI):
- Bump ruff 0.15.14 -> 0.15.15 and ty 0.0.39 -> 0.0.40 in plugin-eval's
  uv.lock so CI installs the same versions we run locally, and reformat the
  tools/ + plugin-eval sources to ruff 0.15.15 (fixes the failing
  ruff format --check; the lock-hash change also busts CI's stale cache).

make validate STRICT=1 clean / garden 0 errors / 442 tests pass; regeneration
remains drift-free.
2026-05-29 13:18:48 -04:00
..

signed-audit-trails

A teaching skill for setting up cryptographically signed audit trails on every Claude Code tool call. Cookbook-style walkthrough with runnable examples.

What this is

A skill (not a runtime hook): a set of instructions and examples that explain the pattern end-to-end. Use this when you are figuring out whether receipts are the right fit for your project. Once you know they are, install the protect-mcp plugin for the actual hooks.

When to use this plugin

  • Learning the pattern before committing to infrastructure
  • Evaluating whether signed audit trails fit your compliance need
  • Teaching team members the three-invariant cryptographic model (JCS canonicalization + Ed25519 signatures + hash chains)
  • Walking a client or auditor through a live demonstration of tamper detection

For production use, the protect-mcp plugin gives you the runtime hooks directly. This plugin is the skill file you invoke via Skill when you want the concept explained in-session.

What is inside

skills/signed-audit-trails-recipe/SKILL.md

A single skill file containing:

  • Step-by-step setup (Cedar policy, hook configuration, first receipt)
  • Live tamper detection walkthrough
  • Receipt format explanation (three invariants)
  • Cross-implementation interoperability table
  • CI/CD integration snippet (GitHub Actions)
  • Composition with SLSA provenance for agent-built software
  • Common pitfalls and references

Standards

  • Ed25519 (RFC 8032) for receipt signatures
  • JCS (RFC 8785) for deterministic JSON canonicalization before signing
  • Cedar (AWS) for policy evaluation
  • IETF draft draft-farley-acta-signed-receipts

License

MIT. Same as the adjacent governance-category plugins in this marketplace.