Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ScottRBK/forgetful --skill forgetful-cli-setupgit clone --depth 1 https://github.com/ScottRBK/forgetfulWrote 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/scottrbk/forgetful/forgetful-cli-setup)<a href="https://agentmods.dev/skills/scottrbk/forgetful/forgetful-cli-setup"><img src="https://agentmods.dev/badge/skills/scottrbk/forgetful/forgetful-cli-setup/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/scottrbk/forgetful/forgetful-cli-setup"><img src="https://agentmods.dev/badge/skills/scottrbk/forgetful/forgetful-cli-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 24 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
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.00084 | $0.00896 |
| Opus 5.5 | $0.00034 | $0.00358 |
| Sonnet 5.5 | $0.00017 | $0.00179 |
| Haiku 4.5 | $0.00008 | $0.00090 |
Grade A, and why
forgetful-cli-setup 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 1mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setting up the Forgetful CLI
The CLI is the shell-native surface: same tool registry as MCP, reachable by anything that can run a command. Setup ends with a verified round-trip, not an installed binary.
Install
uvx forgetful-ai --version # ephemeral, no install
pip install forgetful-ai # or: uv tool install forgetful-ai
Both forgetful and forgetful-ai invoke the same CLI.
Choose a mode
Connection precedence: --local > --server URL > FORGETFUL_SERVER env > local default.
- Local (default): runs in-process against the locally configured database — zero config, no server needed. Right for a personal knowledge base on one machine.
- Remote: drives a deployed server. Interactive use:
forgetful auth login --server <url>(browser OAuth; tokens cached under~/.config/forgetful/, server written to the user config). Headless/CI use: setFORGETFUL_SERVERandFORGETFUL_TOKEN(bearer) in the environment — no browser involved.
Config merges shell env over ~/.config/forgetful/.env. Check state anytime with
forgetful auth status.
Verify — the completion criterion
forgetful tools list # registry categories come back
forgetful project list --json # one real call round-trips
Done when: both succeed against the intended target (local or the remote URL).
The machine contract
For scripts and agents, pass --json on data commands — tools, call, memory, and
project verbs: results are machine JSON, errors arrive as {"error": ...} on stderr. auth
subcommands are human-oriented and don't take --json. Exit codes are contractual — 0
success, 1 tool or runtime error, 2 usage error. Parse output, branch on exit code.
The discovery ladder
- Curated verbs for the common paths:
forgetful memory search|save|get|recent,forgetful project list. forgetful tools list [--category <c>]to discover every registry operation.forgetful tools info <operation>for the schema.forgetful call <operation> --args '<JSON>'to invoke anything the registry has.
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.
- 1mo ago First seen · 84 lines · 84 tokens per session scan A f6441db7ee21
forgetful-cli-setup is a skill published in the GitHub repository ScottRBK/forgetful (302 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 896 once invoked, about $0.0003 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.
Other skills, from other repositories
firebase
Use when building on Firebase — Firestore data modeling, Security Rules, Auth and custom claims, Cloud Functions, Storage, modular Web/Admin SDK imports — including symptoms like a database open to the internet, a query rejected by rules, or a doc stuck at 1 write/sec. NOT managed-Postgres BaaS with SQL and RLS (that…
mesh-memory
Self-hosted semantic memory for AI agents via MCP. Save worklogs, decisions, and notes, then recall them across sessions by meaning, not keyword. Postgres + pgvector with auto-tagging.
sibyl
Persistent memory and task coordination for this project. Invoke for any prompt about past work, project state, in-progress tasks, prior decisions, gotchas, or capturing a non-obvious learning. Also covers semantic search across project knowledge and external docs.
doris-debug-resource-isolation
Use for Doris Workload Group / resource tag queue starvation, CPU/memory isolation leaks, and workload policy debugging. Commands: SHOW WORKLOAD GROUPS, EXPLAIN resource.
crystalline-capture
Use when durable knowledge is learned while working, when the user asks to update a Crystalline domain, or before writing or editing an engram so it is deduplicated, well-formed and linked correctly.
crystalline-schema
Use when a Crystalline domain wants structure for one of its engram types - authoring a Picoschema schema engram, running inferschema to bootstrap one from what is already captured, or validateengrams to check conformance.