Borrowing it
Nothing to install: this file belongs to majiayu000/remem. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/majiayu000/remem/main/.agents/skills/remem-first-run-smoke/SKILL.mdgit clone --depth 1 https://github.com/majiayu000/rememWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/majiayu000/remem/remem-first-run-smoke)<a href="https://agentmods.dev/skills/majiayu000/remem/remem-first-run-smoke"><img src="https://agentmods.dev/badge/skills/majiayu000/remem/remem-first-run-smoke/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/majiayu000/remem/remem-first-run-smoke"><img src="https://agentmods.dev/badge/skills/majiayu000/remem/remem-first-run-smoke.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00052 | $0.00726 |
| Opus 5 | $0.00026 | $0.00363 |
| Sonnet 5 | $0.00010 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
remem-first-run-smoke scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
remem-first-run-smoke
Use this skill to test the path a new user experiences without touching the
developer's real ~/.codex, ~/.claude, or ~/.remem directories.
Rules
- Always use a temporary
HOMEandREMEM_DATA_DIR. - Prefer
--dry-runbefore activation commands that edit host config. - Do not run hook activation against the real home directory during smoke tests.
- Keep stdout/stderr logs when the smoke fails; install and status failures are usually more useful than a later generic test failure.
CLI Smoke
Run from the repository root:
cargo build --release
tmp_home="$(mktemp -d)"
tmp_data="$(mktemp -d)"
HOME="$tmp_home" REMEM_DATA_DIR="$tmp_data" target/release/remem install --target codex --dry-run
HOME="$tmp_home" REMEM_DATA_DIR="$tmp_data" target/release/remem install --target codex
HOME="$tmp_home" REMEM_DATA_DIR="$tmp_data" target/release/remem status
HOME="$tmp_home" REMEM_DATA_DIR="$tmp_data" target/release/remem context --host codex-cli >/tmp/remem-context.txt
HOME="$tmp_home" REMEM_DATA_DIR="$tmp_data" target/release/remem doctor || doctor_status=$?
Expected result:
- install writes only inside the temporary home/data directories
- status completes without requiring manual repair
- context exits successfully and writes deterministic, bounded output
- doctor may exit non-zero before any real SessionStart/Stop heartbeat exists; treat that as expected only when the diagnostic output is limited to the fresh capture-liveness warning. After a synthetic or real hook heartbeat, doctor should pass without that warning.
Remove the temporary directories after inspecting failures.
Plugin Activation Smoke
For Codex plugin activation changes, first install the repo-built runtime into the plugin-managed store, then run activation in dry-run mode against a temp home:
cargo build --release
tmp_home="$(mktemp -d)"
tmp_data="$(mktemp -d)"
HOME="$tmp_home" REMEM_DATA_DIR="$tmp_data" \
REMEM_BINARY="$PWD/target/release/remem" \
node plugins/remem/scripts/remem-runtime.js install
HOME="$tmp_home" REMEM_DATA_DIR="$tmp_data" \
node plugins/remem/scripts/activate-codex.js --dry-run
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 86 lines · 52 tokens per session scan A 25b7fecd38ac
remem-first-run-smoke is a skill published in the GitHub repository majiayu000/remem (30 stars, last pushed 4d ago), licensed MIT. It adds 52 tokens to every session and 726 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
migrate-v0-to-v1
Migrate a Scraps wiki from v0 to v1. Use this whenever the user asks to upgrade Scraps, migrate v0 wiki syntax/config, convert implicit tags to explicit #[[tag]], move from scraps-writer to scraps, or audit a wiki for v1 readiness. This skill is designed for one-pass LLM-led migrations that discover the latest v0 and…
dcg
Destructive Command Guard - High-performance Rust hook for Claude Code that blocks dangerous commands before execution. SIMD-accelerated, modular pack system, whitelist-first architecture. Essential safety layer for agent workflows.
tauri-pilot
Inspect, interact with, and test a running Tauri v2 app via CLI. Communicates over Unix socket using JSON-RPC 2.0. Use when testing UI, automating interactions, or debugging a Tauri app.
ingest
Create a new scrap from a source (prompt, URL, or arbitrary markdown), update cross-links in related scraps, and run a sanity check. Use this when the user wants to add a scrap, summarize an article, save synthesized content to the wiki, or file back a Q&A result.
query
Answer questions about the wiki by searching, reading, and synthesizing relevant scraps with [[Title]] citations. Use this when the user wants to query the wiki, ask what they have written about a topic, compare scraps, find related notes, or pull a synthesized overview from existing scraps.
planning-with-scratchpad
Use when user explicitly requests planning with a scratchpad, or asks for persistent tracking of a complex task that the human can browse visually. Backs planning files with the scratch CLI so a pad's files are registered and viewable.