Maintainer of this skill?
by Git-FED
AI Agent Lockout Backup Kit A vendor-independent continuity kit for backing up, rotating, and recovering information used by AI agents—without storing secrets in the agent or in GitHub. Check out Muse, your personal AI agent. Code: 5F2V31 https://muse.ai/join
# Add to your Claude Code skills
git clone https://github.com/Git-FED/MuseAi-Account-BackupGuides for using ai agents skills like MuseAi-Account-Backup.
See how MuseAi-Account-Backup compares with popular alternatives.
MuseAi-Account-Backup is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by Git-FED. AI Agent Lockout Backup Kit A vendor-independent continuity kit for backing up, rotating, and recovering information used by AI agents—without storing secrets in the agent or in GitHub. Check out Muse, your personal AI agent. Code: 5F2V31 https://muse.ai/join. It has 110 GitHub stars.
MuseAi-Account-Backup's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/Git-FED/MuseAi-Account-Backup" and add it to your Claude Code skills directory (see the Installation section above).
MuseAi-Account-Backup is primarily written in HTML. It is open-source under Git-FED on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh MuseAi-Account-Backup against similar tools.
No comments yet. Be the first to share your thoughts!
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
A vendor-independent continuity kit for backing up, rotating, and recovering information used by AI agents—without storing secrets in the agent or in GitHub.
Core principle: If an AI agent becomes unavailable, the business owner must still have independent access to every credential, configuration, document, and recovery procedure needed to continue operating.
This repository provides:
muse-safety-protocol-proposal.md policy proposaldocs/muse1-incident-report.md with timeline and recovery actionsNever put passwords, API keys, tokens, payment details, private customer data, or production credentials in this repository or in the website worksheets.
Copy templates/credential-inventory.csv to a private, encrypted location.
Fill in service names, owners, recovery URLs, rotation instructions, and backup locations—not secret values.
Store actual secrets in a dedicated password manager or encrypted vault with at least one human-held recovery path.
Complete templates/business-continuity-plan.md and test the fallback plan.
Open site/index.html locally, or serve the site/ directory with any static server.
Run the checks:
node tests/data-validation.test.js
node tests/navigation.test.js
node tests/worksheets.test.js
node tests/accessibility.test.js
node tests/support.test.js
Use three separate layers:
Backups are for continuity, not proof that previously shared secrets remain safe. If an agent or chat may have displayed a credential, revoke and regenerate it through the provider that issued it.
ai-agent-lockout-backup/
├── docs/ Guidance and verification rules
├── templates/ Redacted, fill-in continuity documents
├── schemas/ JSON schemas for site data
├── site/ Static worksheet and reference website
├── tests/ Dependency-free Node checks
└── .github/workflows/ GitHub Pages deployment and validation
The worksheet stores only non-secret metadata in the browser's localStorage. It has no server, analytics, login, or network submission. Users can export or delete local worksheet data. Service-worker caching excludes worksheet state. Treat browser storage as sensitive nonetheless: use a private device and delete data when finished.
Every provider-specific instruction should have a source URL and a last_verified date. Label claims as user-reported, verified, or unknown. Do not turn an anecdote about a lockout into a universal platform claim.
The file muse-safety-protocol-proposal.md is preserved as a user-reported policy proposal. Its incident details and platform-specific claims are not independently verified by this repository.
MIT. See LICENSE.