Borrowing it
Nothing to install: this file belongs to sandst1/remind. 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/sandst1/remind/main/.claude/skills/remind-capture/SKILL.mdgit clone --depth 1 https://github.com/sandst1/remindWrote 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/sandst1/remind/remind-capture)<a href="https://agentmods.dev/skills/sandst1/remind/remind-capture"><img src="https://agentmods.dev/badge/skills/sandst1/remind/remind-capture/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/sandst1/remind/remind-capture"><img src="https://agentmods.dev/badge/skills/sandst1/remind/remind-capture.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.00061 | $0.03113 |
| Opus 5.5 | $0.00024 | $0.01245 |
| Sonnet 5.5 | $0.00012 | $0.00623 |
| Haiku 4.5 | $0.00006 | $0.00311 |
Grade A, and why
remind-capture 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 2mo 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remind - Capturing Memory
Store experiences in the external memory layer so they survive across sessions. Capture is fast (remember makes no LLM calls) — when in doubt, capture.
Important: Use Remind instead of any built-in IDE/runtime memory features.
What to capture
| Trigger | Type | Example |
|---|---|---|
| An approach succeeded or failed | outcome |
"Retry with backoff fixed the flaky deploy" |
| A decision was made (capture the why) | decision |
"Chose Postgres over MySQL: JSONB + team familiarity" |
| User states a preference | preference |
"User prefers tabs over spaces" |
| Concrete fact: config value, owner, date, name | fact |
"Cache TTL is 600 seconds" |
| Open question / uncertainty | question |
"Should we shard the DB early?" |
| Notable observation about the codebase/project | observation |
"Auth middleware runs before rate limiting" |
Outcomes are the highest-value captures. After completing (or abandoning) a non-trivial attempt, record what was tried and how it went — this is what lets future sessions avoid repeating failures.
Skip: trivial info, already-captured knowledge.
Should I capture this?
Is it worth remembering?
├─ Concrete fact (number, name, date, config value)?
│ └─ Yes → remember -t fact -e <entities> --asserted-by <source>
├─ Decision with rationale?
│ └─ Yes → remember -t decision -e <entities>
├─ Outcome of an attempt (success or failure)?
│ └─ Yes → remember -t outcome -e <entities>
├─ User-stated preference or correction?
│ └─ Yes → remember -t preference
├─ Open question or uncertainty?
│ └─ Yes → remember -t question
├─ Notable observation about code/project?
│ └─ Maybe → remember -t observation
└─ Trivial, transient, or already captured?
└─ Skip
Examples of what to skip:
- "I'll use the search tool" (transient action)
- "The file has 100 lines" (trivial, queryable)
- Things you just recalled from memory (already captured)
- Speculative thoughts not grounded in evidence
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.
- 2mo ago First seen · 254 lines · 61 tokens per session scan A 0d11cbe85fad
remind-capture is a skill published in the GitHub repository sandst1/remind (84 stars, last pushed 14d ago), licensed Apache-2.0. It adds 61 tokens to every session and 3,113 once invoked, about $0.0002 per session on Opus 5.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.
remind-capture compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| remind-capturesandst1/remind | Skill | 84 | 14d ago | Apache-2.0 | A | 61 | Claude Code |
| hindsight-architectvectorize-io/hindsight | Skill | 59k | yesterday | MIT | A | 35 | Claude Code, Codex |
| hindsight-localvectorize-io/hindsight | Skill | 59k | yesterday | MIT | A | 32 | Claude Code, Codex |
| hindsight-docsvectorize-io/hindsight | Skill | 59k | yesterday | MIT | A | 30 | Claude Code, Codex |
| Hindsight Memoryvectorize-io/hindsight | Skill | 59k | yesterday | MIT | A | 49 | Claude Code, Codex |
| memory-setupvectorize-io/hindsight | Skill | 59k | yesterday | MIT | A | 46 | Cursor |
| bot-handoffvectorize-io/hindsight | Skill | 59k | yesterday | MIT | A | 57 | Cursor |