Borrowing it
Nothing to install: this file belongs to the-sid-dani/second-brain-os. 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/the-sid-dani/second-brain-os/main/.agents/skills/save-resource/SKILL.mdgit clone --depth 1 https://github.com/the-sid-dani/second-brain-osWrote 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/the-sid-dani/second-brain-os/save-resource)<a href="https://agentmods.dev/skills/the-sid-dani/second-brain-os/save-resource"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/save-resource/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/the-sid-dani/second-brain-os/save-resource"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/save-resource.svg" alt="Reviewed on agentmods" width="80" 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.00134 | $0.02713 |
| Opus 5.5 | $0.00054 | $0.01085 |
| Sonnet 5.5 | $0.00027 | $0.00543 |
| Haiku 4.5 | $0.00013 | $0.00271 |
Grade A, and why
save-resource 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
save-resource
Workhorse for getting things into Resources. Input is a source (file or content) + type + topic; output is a file at the canonical destination under <workspace.root>/<workspace.resources>/.
Before you begin: read the Configuration section in root CLAUDE.md. Path tokens like <workspace.resources> resolve to whatever's defined there — don't hardcode.
Why this exists
Resources is two-level (<workspace.resources>/<type>/<content>) and each type has a different convention — research uses YYYY-MM-<topic>-research/ folders, reference is flat, meetings is YYYY-MM-DD-<topic>.md. Doing this by hand means the user has to remember which type uses which convention. The skill enforces it.
This also means Inbox doesn't graveyard. The Inbox→Resources flow has a one-step path (/save-resource) instead of "manually decide where it goes, mkdir if needed, mv it, hope you got the naming right". Without it, items pile up in the Inbox forever.
The skill also accepts CHAT CONTENT as a source, not just paths. If the user pastes notes and says "save this to research/X", the skill writes a new file at the destination — no Inbox round-trip required.
When to use
Trigger phrases (intentionally broad — over-trigger rather than miss):
- "save this to research" / "save this in reference" / "save this meeting note"
- "promote this to resources" / "this belongs in resources/"
- "file this as " / "save the X file in inbox to "
- "save as a " / "this is a meeting note for X"
- "/save-resource"
Do NOT trigger for:
- New project creation — that's
/new-project(which has acode-repobranch for repos) - Memory updates within an existing project — append directly to that project's
memory.md - Outputs <assistant.name> generates have dedicated subdirs inside Resources: briefings →
<workspace.resources>/briefings/, meeting-prep →<workspace.resources>/meeting-prep/, organization-reports →<workspace.resources>/organization-reports/./save-resourceis for user-supplied reference material (links, articles, snippets) — those land in<workspace.resources>/research/or<workspace.resources>/reference/.
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 Changed e87d63366dbd
- 1mo ago First seen · 196 lines · 134 tokens per session scan A 3546aaaf9d7b
save-resource is a skill published in the GitHub repository the-sid-dani/second-brain-os (3 stars, last pushed 7d ago), licensed MIT. It adds 134 tokens to every session and 2,713 once invoked, about $0.0005 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-31.
Other skills, from other repositories
screenpipe-api
Query the user's local and synced-device data via the screenpipe REST API at localhost:3030 — recordings, audio, UI, meetings, connected services, and memory. Use for screen activity, other-device or cross-device history, productivity, media export, connections, durable memory, or discovering and automating saved…
follower-onboard
Onboard a new machine as a receive-only follower on a multi-machine agent network: it reads the shared vault, canon, skills and memory, runs nothing heavy locally (no RAG, reindex or GPU), and never receives executable hooks from the hub. Checklist-driven, with a verify step at each stage. Triggers: "/follower-onboard…
brain-onboard
An onboarding workflow that helps another person create and use their own private knowledge store, sometimes called a second brain. It gathers their information with consent, saves it in their own workspace, and demonstrates a first useful result.
memory-tidy
Tidy an agent's always-loaded memory index (MEMORY.md) on macOS or Linux: trim long lines, move closed entries to an archive, fold domains into hub files, restore dropped pins and add pointers for orphan memory files. Use when the index is over budget or has orphans. Triggers: /memory-tidy, /mt, tidy memory.
claudeai-sync
Pull new and changed claude.ai web conversations into an Obsidian vault, extract artifacts as first-class notes, concept-link them, and refresh the RAG index and dashboard. Idempotent: curated notes are never overwritten. Triggers: "/claudeai-sync", "pull claude.ai", "grab new claude.ai chats".
chat-search
Search inside past agent sessions and continue the one that matters with a single command. Uses a separate episodic session index, so raw chat noise never pollutes the curated RAG. Triggers: "/chat-search", "which chat discussed X", "did we already research X", "search old chats".