169077e9fb
Add a When to Use section for akf-trust-metadata so release validation stays within the current warning budget.\n\nRefresh the generated plugin-safe and catalog artifacts produced by the maintainer sync after the PR batch landed.
1.6 KiB
1.6 KiB
name, description, risk, source, date_added, author, tags
| name | description | risk | source | date_added | author | tags | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| akf-trust-metadata | The AI native file format. EXIF for AI — stamps every file with trust scores, source provenance, and compliance metadata. Embeds into 20+ formats (DOCX, PDF, images, code). EU AI Act, SOX, HIPAA auditing. | safe | community | 2026-03-27 | HMAKT99 |
|
AKF — The AI Native File Format
Every photo has EXIF. Every song has ID3. AKF is the native metadata format for AI-generated content.
When to Use
Use this skill when you need to stamp, inspect, or audit provenance and trust metadata on AI-generated or AI-modified files for compliance, review, or handoff workflows.
After creating or modifying files
akf stamp <file> --agent <agent-name> --evidence "<what you did>"
Evidence examples:
- "generated from user prompt"
- "refactored existing code"
- "tests pass"
- "docs reviewed"
Before modifying existing files
akf read <file> # Check existing trust metadata
akf inspect <file> # See detailed trust scores
Compliance auditing
akf audit <file> --regulation eu_ai_act # EU AI Act Article 50
akf audit <file> --regulation hipaa # HIPAA
akf audit <file> --regulation sox # SOX
akf audit <file> --regulation nist_ai # NIST AI RMF
Classification
--label confidentialfor finance/secret/internal paths--label publicfor README, docs, examples- Default:
internal
Install
pip install akf
Links
- https://akf.dev
- https://github.com/HMAKT99/AKF
- npm:
npm install akf-format