bm-remember-44a81a — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited bm-remember-44a81a (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.
Capture $ARGUMENTS into Basic Memory as a quick note, keeping the user's words.
When no project is pinned, discover projects with bm_project(command="list") and pass the selected project's external ID as project on note/search calls. With several addressable projects, these calls require an explicit scope even when a default is configured.
basicMemory block with the same precedence thehooks use. For the user-level base, append settings.json to the literal value of CLAUDE_CONFIG_DIR when that environment variable is present; do not trim it, expand ~, or treat an empty value as unset. Use ~/.claude/settings.json only when the variable is absent. Then the project's .claude/settings.json and .claude/settings.local.json override it per key. A user-level block alone is enough; a project can still pin its own values:
rememberFolder — folder for quick captures (default: bm-remember)primaryProject — project to write to (when absent, discover projects and explicitlyselect the listed default or sole project)
Both are optional. Use the defaults if the block or a key is missing. Don't fail if there's no settings file.
bm-writing skill before drafting; match itsdepth to this lightweight capture — keep the user's wording and do not pad a small fact into an essay.
$ARGUMENTS, verbatim. Don't rewrite or pad it.…if you truncate). If it's one long line, write a short descriptive title instead.
$ARGUMENTS is empty (e.g. you were invoked because the user said "rememberthat…"), capture the specific thing they asked you to remember from the conversation. If it's genuinely unclear what to save, ask one short question.
bm_write:title = the derived titledirectory = the resolved rememberFoldercontent = the texttags = ["manual-capture"]primaryProject if set: pass it as project, including whenit is an external_id UUID. Omit project if primaryProject isn't set. Don't overwrite an existing note unless the user explicitly asks.
e.g. Saved → bm-remember/<slug>.
relations, or structure unless they ask.
bm-decide skillinstead (the basic-memory output style also captures these inline). Wrapping up a work session is bm-checkpoint's job, not this skill's.
server prefix; use the advertised bm_write tool.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.