bm-status-fd9041 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited bm-status-fd9041 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Gather a concise diagnostic. Do not over-investigate.
basic-memory --versionbm --versionuvx --prerelease=allow basic-memory --versionKeep going if no launcher resolves. The plugin hook scripts can still use their uv-managed environment; report hook health as unavailable instead of claiming the hooks cannot work.
~/.codex/basic-memory.json, then the nearest project.codex/basic-memory.json; project keys override user keys
primaryProject, secondaryProjects, teamProjects,captureFolder, rememberFolder, recallTimeframe, focus, sessionProfile, repository, checkpointOnCompact, and captureEvents
rememberFolder=codex/remember,and checkpointOnCompact=true
basic-memory hook status --harness codex --project-dir <repo-root>
flush, settings state, resolved primary project, capture state, capture folder, checkpoint-prompt state, Basic Memory version, and uv version from that command
backlog solely to Codex
it disagrees with the manually read config, show the mismatch
uv --version in the current environment independently of CLIreachability; uv is a required hook prerequisite
verified"; shell success does not establish the Desktop hook process's PATH
launch error and PATH; uv: command not found occurs before the Python script can emit a diagnostic
../../README.md under "Troubleshooting Desktop hooks on WSL"for the default-location probe and conditional symlink workaround
post-compaction checkpoint note were observed; otherwise label it unverified
plugins/codex/hooks/hooks.json exists if running from this repothey run
type=codex_session; whensessionProfile=coding, also query type=coding_session with repository=<configured repository>, then merge, deduplicate, sort newest first, and keep the newest five; never run an unscoped coding-session query when the repository is missing; these are agent-authored checkpoints, while lifecycle envelopes remain local operational trace
type=task, status=activetype=decision, status=openUse this shape:
Basic Memory for Codex
- CLI: <version or missing>
- Project: <primaryProject or default>
- Reads from: <secondaryProjects or none>
- Share targets: <teamProjects or none>
- Capture folder: <captureFolder>
- Remember folder: <rememberFolder>
- Recall timeframe: <recallTimeframe>
- Session profile: <general | coding>
- Repository: <owner/name or none>
- Checkpoint on compact: <enabled | disabled>
- Event capture: <enabled | disabled>
- Shared hook inbox: <path or unavailable>
- Shared pending envelopes: <count or unavailable>
- Shared archived envelopes: <count or unavailable>
- Last flush: <timestamp, never, or unavailable>
- Hook runtime in this environment: basic-memory <version>; uv <version or missing>
- Desktop hook execution: <verified from context and checkpoint | unverified>
- Recent checkpoints: <count across coding_session and codex_session>
- Active tasks: <count>
- Open decisions: <count>
- Hooks: installed; trust review required in CodexList recent checkpoints by type, title, and permalink when available. Warn when event capture is enabled and pending envelopes are accumulating or the last flush is never, while noting that another harness may contribute to the shared counts. Do not warn about an empty inbox when capture is disabled.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.