metadata-audit

Implement hash-only metadata storage for audit trails in the Payload harness.

Updated May 11, 2026
One-click install
npx skills add https://github.com/AesopScott/mojo --skill metadata-audit-aesopscott
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metadata-audit
Source: https://github.com/AesopScott/mojo/tree/main/harnesses/skills/metadata-audit
Command: npx skills add https://github.com/AesopScott/mojo --skill metadata-audit-aesopscott

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses high operational costs and storage bloat by replacing full payload logging with efficient hash-based metadata tracking.

Core Features & Use Cases

  • Cost Efficiency: Reduces token usage and storage overhead by auditing hashes instead of raw request/response bodies.
  • Auditability: Maintains a verifiable trail of system interactions while keeping the data footprint minimal.
  • Use Case: Use this when you need to prove what was sent to an LLM for compliance or debugging without incurring the storage costs of logging every full prompt and completion.

Quick Start

Run the metadata-audit skill to inspect the current payload harness and implement hash-only logging for your target boundary.

Frequently Asked Questions about metadata-audit

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

FAQPage Schema
How does hash-based metadata auditing reduce LLM payload storage costs?

Hash-based metadata auditing reduces storage costs by logging cryptographic hashes instead of full prompt and completion bodies. This minimizes token usage and storage overhead while maintaining a verifiable trail of system interactions for compliance.

Can I verify what was sent to an LLM for compliance without retaining full payloads?

Yes, you can verify compliance without full payloads by implementing hash-only metadata storage. This approach maintains a verifiable audit trail of system interactions, proving what was sent while keeping the data footprint minimal.

How do I set up hash-only logging for system monitoring and compliance trails?

To set up hash-only logging, run the audit skill to inspect your payload harness and define precise boundaries. This implements hash-based tracking for system monitoring and compliance logging without full payload retention.

What is the difference between full payload logging and hash-only metadata tracking?

Hash-only metadata tracking replaces full payload logging by storing cryptographic hashes instead of raw request and response bodies. This approach ensures data integrity and auditability while drastically reducing storage bloat and operational costs.

When should I not use hash-only auditing for my payload harness?

You should not use hash-only auditing when you need to inspect the actual content of prompts or completions for debugging. Hash-based audit trails prove data integrity but do not retain the raw payload data required for content analysis.

Does metadata-audit require specific boundary definitions to ensure data integrity?

Yes, metadata-audit requires precise boundary definition to ensure data integrity. Verifying hash-based audit trails within the payload harness depends on accurately scoped boundaries to prove compliance without full payload retention.