skills.rest
ArogyaReddy
ArogyaReddyCOMMUNITY
Explore all skills by this author →
GitHub

signed-audit-trails-recipe

Generate Ed25519 receipts for Claude Code tool calls with Cedar policy evaluation.

Updated Apr 19, 2026
Search Tags:#provenance#receipts#cryptography#ci-cd#ed25519#signed-audit-trails
One-click install
npx skills add https://github.com/ArogyaReddy/https-github.com-wshobson-agents --skill signed-audit-trails-recipe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signed-audit-trails-recipe
Source: https://github.com/ArogyaReddy/https-github.com-wshobson-agents/tree/main/plugins/signed-audit-trails/skills/signed-audit-trails-recipe
Command: npx skills add https://github.com/ArogyaReddy/https-github.com-wshobson-agents --skill signed-audit-trails-recipe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cryptographic receipts provide verifiable, tamper-evident evidence of every Claude Code tool call, enabling auditors and stakeholders to prove behavior without relying on operator trust.

Core Features & Use Cases

  • Policy-gated tool use with Cedar evaluation before execution.
  • Ed25519 receipts generated after each tool call, forming a verifiable chain.
  • Offline verification & SLSA provenance compatible with standard attestation tooling.
  • CI/CD integration for audit-ready build and deployment pipelines.

Quick Start

Install the protect-mcp hook configuration, write a Cedar policy, and begin using Claude Code to generate verifiable receipts.

Frequently Asked Questions about signed-audit-trails-recipe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create tamper-evident audit trails for Claude Code tool calls?▼

You generate verifiable receipts for Claude Code calls by installing the protect-mcp hook configuration, which produces Ed25519 cryptographic receipts after each tool execution to form a tamper-evident chain.

What are cryptographic receipts and how do they secure CI/CD pipelines?▼

Cryptographic receipts are Ed25519-signed records of tool calls that provide verifiable provenance in CI/CD pipelines, enabling offline verification and SLSA-compliant attestation for audit-ready builds and deployments.

Can I use Cedar policy evaluation to gate tool use in Claude Code?▼

Yes, Cedar policy evaluation can be integrated to gate tool use before execution in Claude Code workflows, ensuring only policy-compliant tool calls generate cryptographic receipts and proceed within the pipeline.

Does this approach support offline verification of SLSA-compliant provenance?▼

Offline verification of SLSA-compliant provenance is fully supported, allowing auditors to verify Ed25519 receipts and tamper detection without network access or reliance on the original operator environment.

What's the best way to add verifiable behavior proofs for multi-party collaborations?▼

The best way to add verifiable behavior proofs for multi-party collaborations is generating Ed25519 receipts chained together after each tool call, enabling all parties to independently verify provenance and detect tampering offline.

Related Skills

Explore More Legal & Compliance Skills→
PriyanshKuniyalPriyanshKuniyal

signed-audit-trails-recipe

Sign Claude Code tool calls with Ed25519 receipts and Cedar policy evaluation.

Community
Advanced
marquesfelipmarquesfelip

artifact-signing

Automate artifact signing and provenance verification with Sigstore and Cosign.

Community
Advanced
haxlyshaxlys

signed-audit-trails-recipe

Create verifiable audit logs for Claude Code tool calls with Ed25519 receipts.

Community
Advanced
jay6697117jay6697117

agency-agentic-identity-trust-architect

Design and deploy cryptographic identity, authentication, and trust verification for autonomous agents.

Community
Advanced