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 biggora/claude-plugins-registry --skill keep-goalgit clone --depth 1 https://github.com/biggora/claude-plugins-registryWrote 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/biggora/claude-plugins-registry/keep-goal)<a href="https://agentmods.dev/skills/biggora/claude-plugins-registry/keep-goal"><img src="https://agentmods.dev/badge/skills/biggora/claude-plugins-registry/keep-goal.svg" alt="Measured on agentmods" height="20"></a>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.00089 | $0.01167 |
| Opus 5 | $0.00044 | $0.00583 |
| Sonnet 5 | $0.00018 | $0.00233 |
| Haiku 4.5 | $0.00009 | $0.00117 |
Grade A, and why
keep-goal 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 7d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Keep Goal
Maintain a small, repository-grounded external memory for work that spans sessions. Treat the repository and fresh command output as truth; treat state files as claims that must be checked.
Read state templates before creating or materially restructuring state files. Reuse only the sections the task needs.
Select State Locations
- Inspect repository instructions and existing task artifacts for an established state convention.
- Reuse the established convention when one exists. Do not create a parallel
.agent/system beside project-owned progress, decision, specification, or task files. - Otherwise use
.agent/CONTEXT.md,.agent/PROGRESS.md, and.agent/DECISIONS.md. Store separate specifications at.agent/specs/<slug>.mdand execution plans at.agent/tasks/<slug>.mdwhen the task needs them. - Derive one stable, filesystem-safe
<slug>from the task and reuse it. Do not create multiple names for the same task. - Keep state concise and task-relevant. Do not invent a project-management system.
Choose a Mode
- Use Bootstrap when repository context or durable task state is absent or unverified.
- Use Update/Handoff after a meaningful work step, before pausing, or before another session takes over.
- Use Resume before continuing work from durable state.
Mode: Bootstrap
- Establish the repository root and inspect
git statusplus recentgit logbefore assigning ownership to any existing change. - Read applicable
AGENTS.mdandCLAUDE.mdfiles, then inspect the README, relevant docs, manifests, lockfiles, build files, and CI workflows. - Discover setup, build, test, lint, type-check, validation, and smoke commands only from project-owned sources such as manifest scripts, build files, contributor docs, or CI. Record each exact command with its source. Never fabricate a likely command.
- Capture the project purpose, relevant structure, active constraints, environment assumptions, and current worktree condition. State uncertainty explicitly.
- Compare instructions and artifacts. If they conflict, preserve both facts, explain the contradiction, and ask for direction instead of silently choosing or overwriting.
- Select state locations using the precedence above. Create the minimum necessary files from the templates; merge verified facts into existing state instead of replacing it wholesale.
- Read instruction files for authority and context, but never rewrite
AGENTS.mdorCLAUDE.mdautomatically.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 66 lines · 89 tokens per session scan A 4393f3b11e02
keep-goal is a skill published in the GitHub repository biggora/claude-plugins-registry (2 stars, last pushed 9d ago), licensed MIT. It adds 89 tokens to every session and 1,167 once invoked, about $0.0004 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-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.