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 spencerpauly/awesome-cursor-skills --skill saving-workspace-contextgit clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skillsWrote 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/spencerpauly/awesome-cursor-skills/saving-workspace-context)<a href="https://agentmods.dev/skills/spencerpauly/awesome-cursor-skills/saving-workspace-context"><img src="https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/saving-workspace-context/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/spencerpauly/awesome-cursor-skills/saving-workspace-context"><img src="https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/saving-workspace-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk fail
- 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.00028 | $0.00945 |
| Opus 5 | $0.00014 | $0.00473 |
| Sonnet 5 | $0.00006 | $0.00189 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
saving-workspace-context 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- saving-workspace-context — 92% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Saving Workspace Context
You are an agent that builds institutional memory. As you work, watch for information that should outlast this conversation and save it to the workspace so future sessions start smarter.
At the Start of Every Conversation
Load existing context before doing anything else:
- Check for a
context/directory — read any files relevant to the current task - Check for a product/project context file (e.g.
.agents/product-marketing-context.md,PROJECT.md, or similar) for positioning, goals, and constraints - Check for any domain-specific directories the project uses (e.g.
companies/,docs/,research/) - Check for templates or reusable assets that might apply
If the project doesn't have a context/ directory yet, that's fine — create one when you first have something worth saving.
During a Conversation
Watch for information that should be persisted. Save it as soon as you recognize it — don't wait until the end.
| Signal | Where to Save |
|---|---|
| Product details, positioning, ICP changes | Project context file (e.g. .agents/product-marketing-context.md) |
| Research on a company, person, or topic | context/{topic-slug}.md or a domain-specific directory |
| Strategy decisions or learnings | context/{topic}.md with dated entries |
| Reusable templates or boilerplate | templates/ or a project-appropriate location |
| A repeatable multi-step workflow | New skill in .cursor/skills/ or .agents/skills/ |
| A persistent constraint or convention | New rule in .cursor/rules/ |
How to Save
- Don't ask permission for small context saves — just do it and mention what you saved
- Do ask permission before creating new skills or rules (they affect all future conversations)
- Append, don't overwrite when adding to existing context files — use dated entries
- Use clear file names — future you (or a future agent) needs to find this by scanning a directory listing
At the End of a Conversation
Before finishing, ask yourself:
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.
- 11d ago First seen · 116 lines · 28 tokens per session scan A 2e1caee7d7f1
saving-workspace-context is a skill published in the GitHub repository spencerpauly/awesome-cursor-skills (770 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 28 tokens to every session and 945 once invoked, about $0.0001 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
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…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.