DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check pack integrity and tests before trusting an install with AI Memory Skillpack

Run the hash check and coach test suite to confirm the pack has not been altered.

Who it is forA maintainer or security-minded developer who wants proof a copied or updated memory pack matches its published hashes before it runs on a machine.

The problemA pack that was edited or corrupted in transit could install unexpected files, and a plain prompt gives no way to prove it is intact.

The outcomeA clear pass or fail from the hash check and regression tests, with failures stopping the install.

What you need first

  • Linux or WSL with bash 4.4 or newer, git, rg, and sha256sum
  • Codex CLI installed on the machine
  • Optional: Claude Code, which uses the same skill source through symlinks
  • Optional: Python 3.10 or newer, only for project-mastery-coach
  • macOS needs GNU sha256sum, flock, readlink -f, and a newer bash, or the installer stops

Steps

  1. Run git clone https://github.com/tudoumashu/ai-memory-skillpack.git
  2. Run cd ai-memory-skillpack
  3. Run sha256sum -c SHA256SUMS and stop if any line does not report OK
  4. Run bash tests/run.sh python3 skills/project-mastery-coach/scripts/project_mastery_state.py
  5. Read VERIFY.md and confirm the post-install assertions match what you expect before running the installer

Prompt for your agent

In the ai-memory-skillpack repo, run sha256sum -c SHA256SUMS and the tests/run.sh command for project_mastery_state.py. Expected output: each hash line reported OK and the test runner exit status. Verify that the agent reports failure and makes no install changes if any hash fails.

Caveat. The README says a changed listed file fails the installer integrity gate unless SHA256SUMS is regenerated, so local edits to the pack will fail this check.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page