history SKILL.md skillA
history from vibemaestro/vibemaestro-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vibemaestro/vibemaestro-kit/history@git:20261115.f7fadb6Pins git:20261115.f7fadb6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vibemaestro/vibemaestro-kit
- Path
plugins/vibemaestro-sdlc/skills/history/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261115.f7fadb6, committed Nov 15, 2026
- Size
- 4,969 bytes
- Repository stars
- 4
- License
- Apache-2.0
Use when: in the kit's everyday mode the person asks what was saved or wants an earlier state of their work, in any words: "what versions do I have", "I want the report as it was this morning", "I lost a file", "undo what you did to the report". Lists the quiet saves the kit made after each turn and writes the chosen one as a copy into ban-cu/ inside the folder; it never overwrites the work folder. The person takes the files they need; a copy is removed only on their word. Never change the…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# history — the quiet saves of an everyday folder
In everyday mode the kit saves the person's folder after each turn, locally, in a hidden git history it created in that folder
(never one that was there before, never pushed anywhere; files with common secret names, such as keys, `.env` files and
credentials, are not saved). This skill is how the person sees those saves and gets an earlier state back: the chosen save is
written as a copy into `ban-cu/` inside the folder, and the work folder itself is never overwritten. Speak the person's language,
in plain words: say "save", "old copy" and "take a file back", not commit, branch or restore.
## List the saves
```bash
/bin/sh "${CLAUDE_PLUGIN_ROOT}/scripts/pyrun.sh" "scripts/quiet_save.py" list --dir "<the person's folder>"
```
Each line is one save, newest first: its number, its time to the second, the files that changed (added, changed, removed), and
its id in brackets. `list 50` shows more. Run it from the folder or any folder inside it. "this folder has no saves yet" means
the kit has not saved here (a new folder, or a folder whose history belongs to the person or to the developer flow): say so.
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_uhcefuo3y7v47vrm/a53e937191e423502c058ca0549c52e0e02a0f20edd3c3350a69934efdc93a68.json
Then /plugin install history@markdownregistry-uhcefuo3y7v47vrm in Claude Code. It installs git:20261115.f7fadb6, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add vibemaestro/vibemaestro-kit/history@sha256:a53e937191e42350The line at the top of this page pins the label git:20261115.f7fadb6, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_uhcefuo3y7v47vrm)
0 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in vibemaestro/vibemaestro-kit/history since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of history from somewhere else? Ask it: where did my history come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 15, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/history/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4969 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
vibemaestro/vibemaestro-kit · 4 stars · license Apache-2.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uhcefuo3y7v47vrm GET https://markdownregistry.com/api/v1/resolve?ref=vibemaestro/vibemaestro-kit/history GET https://markdownregistry.com/api/v1/blob/a53e937191e423502c058ca0549c52e0e02a0f20edd3c3350a69934efdc93a68
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from vibemaestro/vibemaestro-kit
Every file in vibemaestro/vibemaestro-kit