signed-audit-trails-recipe

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

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/PriyanshKuniyal/gemini-cli-resources --skill signed-audit-trails-recipe-priyanshkuniyal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signed-audit-trails-recipe
Source: https://github.com/PriyanshKuniyal/gemini-cli-resources/tree/main/extensions/claude-code-workflows/plugins/signed-audit-trails/skills/signed-audit-trails-recipe
Command: npx skills add https://github.com/PriyanshKuniyal/gemini-cli-resources --skill signed-audit-trails-recipe-priyanshkuniyal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires cedar-policy, protect-mcp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in setting up cryptographically signed audit trails for Claude Code tool calls, ensuring secure and verifiable tracking of agent behavior and providing tamper-evident evidence for regulated environments.

Core Features & Use Cases

  • Cryptographic Signing: Signs every tool call with Ed25519 receipts.
  • Policy Evaluation: Evaluates calls against a Cedar policy.
  • Offline Verification: Enables offline verification of the tool call receipts.
  • CI/CD Integration: Facilitates integration with CI/CD pipelines for audit trails.
  • SLSA Composition: Supports SLSA provenance for agent-built software.
  • Use Case: Implement in CI/CD pipelines to verify that each automated build step adheres to the policy, ensuring security and compliance.

Quick Start

Use the protect-mcp sign command to sign Claude Code tool calls.

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 cryptographically signed audit trails for Claude Code tool calls?

To create signed audit trails, use the `protect-mcp sign` command to generate Ed25519 receipts for Claude Code tool calls. This provides tamper-evident evidence suitable for regulated environments and CI/CD pipelines.

What is offline verification for tool call receipts and when is it needed?

Offline verification validates cryptographic tool call receipts without network access. It is needed in regulated environments and multi-party collaborations requiring tamper-evident evidence of agent behavior.

Does CI/CD pipeline audit logging support Cedar policy evaluation?

Yes, CI/CD pipeline audit logging can evaluate automated build steps against a Cedar policy. This ensures each action adheres to defined security and compliance policies before generating a signed receipt.

How do I verify SLSA provenance for agent-built software in CI/CD?

SLSA provenance for agent-built software is verified by integrating signed audit trails into your CI/CD pipelines. This ensures automated build steps adhere to policy and provides tamper-evident evidence of agent behavior.

Do I need cedar-policy and protect-mcp to set up signed audit trails?

Yes, setting up signed audit trails requires cedar-policy for policy evaluation and protect-mcp for cryptographic signing. These dependencies ensure policy-compliant execution and offline verifiability of tool calls.

Can I use Ed25519 cryptographic signing for multi-party collaboration audits?

Yes, Ed25519 cryptographic signing supports multi-party collaborations by providing tamper-evident evidence of agent behavior. The signed receipts ensure verifiable tracking across all collaborating parties.