Rickmanelius Markdown Provenance
- 10 repo stars
- Updated January 29, 2026
- rickmanelius/markdown-provenance
Markdown Provenance is a Claude Code plugin that fingerprints markdown via IPFS and stores permanent copies on Arweave.
About
Markdown Provenance is a Claude Code plugin that adds a slash command for establishing strong provenance on any markdown file. developers and teams who publish specs, changelogs, or public docs can fingerprint content on IPFS and persist copies to Arweave without leaving the agent session. Use it when you need tamper-evident lineage for documentation, open-source writeups, or contracts rendered as markdown—not when you only need local Git history. The workflow targets permanent, decentralized storage keywords (provenance, tagging, upload) rather than a full CMS or compliance suite. Install when you are ready to anchor a markdown artifact after editing; pair with normal Git workflow for day-to-day drafts. Complexity is intermediate because you must understand IPFS hashes, Arweave funding, and what provenance does and does not prove legally.
- Slash command workflow for markdown provenance inside Claude Code
- IPFS fingerprinting for content identity before permanent storage
- Arweave upload for long-term, decentralized archival
- Tagging and file-oriented provenance for solo publishers
- Single-plugin bundle focused on markdown—not generic file vaults
Rickmanelius Markdown Provenance by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install rickmanelius-markdown-provenance@rickmanelius/markdown-provenanceAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 10 |
|---|---|
| Last updated | January 29, 2026 |
| Repository | rickmanelius/markdown-provenance ↗ |
What it does
Fingerprint markdown with IPFS and archive to Arweave so developers can prove when and what they published.
Who is it for?
publishers shipping markdown docs, manifests, or READMEs who want decentralized proof of what they published.
Skip if: Skip if you only need internal wiki versioning with no on-chain or permanent-storage requirements.
What you get
After install, you can run a provenance slash command on a markdown file and obtain IPFS-linked fingerprints plus Arweave-backed archival references.
- IPFS-linked fingerprint for the markdown file
- Arweave-stored copy reference for long-term retrieval
- Provenance metadata suitable for tagging and audit trails
Recommended Plugins
0oastro Kawai Girl Output StyleTransform Claude's responses into kawaii anime girl style\!3
0xbigboss Claude CodeComprehensive configuration system for Claude Code51
2lab Ai Oh My ClaudeClaude Code plugin for AI-powered iterative development loops.37
45ck Claude Sdlc PluginClaude Code plugin for SDLC workflow automation with Storybook planning hub1
70 10 Claude Code Plugins70-10's Claude Code plugins
Aaronbassett Agent FoundryMy personal plugin marketplace for Claude Code4How it compares
Docs provenance slash command, not a general IPFS browser or Arweave wallet app.
FAQ
Who is Rickmanelius Markdown Provenance for?
Developers and small teams using Claude Code who publish markdown and want IPFS fingerprints and Arweave storage without a separate toolchain.
When should I use Rickmanelius Markdown Provenance?
Use it when a markdown file is final enough to anchor—specs, releases, or public docs—after edits and before you treat the file as authoritative.
How do I add Rickmanelius Markdown Provenance to my agent?
Register the rickmanelius/markdown-provenance Claude Code plugin from the community catalog, then invoke its slash command on the target markdown file per the plugin docs.