hesoyam-for-claude-code: Skill for Claude Code

.claude/skills/promote-to-vault/SKILL.md

promote-to-vault is a skill for Claude Code from Shashank2577/hesoyam-for-claude-code. It costs 24 tokens per session (483 once invoked), scanned A, original, MIT.

A review process that examines recent claude-mem observations and saves useful findings into an Obsidian vault. Obsidian is a local note-taking tool for organizing linked documents.

In plain words
What is it for?
Use it to record architecture decisions, debugging breakthroughs, and reusable coding patterns as organized vault notes.
Why use it?
It helps preserve important technical knowledge instead of leaving decisions, debugging discoveries, or reusable patterns in session history.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is Shashank2577/hesoyam-for-claude-code's own configuration. It tells Claude Code how to work on hesoyam-for-claude-code itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything hesoyam-for-claude-code configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Shashank2577/hesoyam-for-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Shashank2577/hesoyam-for-claude-code/main/.claude/skills/promote-to-vault/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Shashank2577/hesoyam-for-claude-code

Made for: Claude Code.

Wrote 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.

agentmods badge for promote-to-vault

README.md
[![agentmods](https://agentmods.dev/badge/skills/shashank2577/hesoyam-for-claude-code/promote-to-vault/github.svg)](https://agentmods.dev/skills/shashank2577/hesoyam-for-claude-code/promote-to-vault)
Your own site
<a href="https://agentmods.dev/skills/shashank2577/hesoyam-for-claude-code/promote-to-vault"><img src="https://agentmods.dev/badge/skills/shashank2577/hesoyam-for-claude-code/promote-to-vault/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.

agentmods 80×15 button for promote-to-vault

Your own site · 80×15
<a href="https://agentmods.dev/skills/shashank2577/hesoyam-for-claude-code/promote-to-vault"><img src="https://agentmods.dev/badge/skills/shashank2577/hesoyam-for-claude-code/promote-to-vault.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 483 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00483
Opus 5 $0.00012 $0.00242
Sonnet 5 $0.00005 $0.00097
Haiku 4.5 $0.00002 $0.00048

Measured 12d ago against content hash da25e60560c8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

promote-to-vault 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 12d 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.

.claude/skills/promote-to-vault/SKILL.md · 43 lines

What it actually says

$VAULT_PATH defaults to ~/Documents/obsidian-vault. Override by setting VAULT_PATH in your environment or passing --vault-path during install.

Review claude-mem observations from the last 7 days using the claude-mem MCP search tools.

If claude-mem is not available: Inform the user that claude-mem is required for this skill (npm install -g claude-mem), then exit gracefully. Do not attempt to proceed without a data source.

For each observation, classify it:

  1. Architecture decisions — Save as a decision record in $VAULT_PATH/03_Resources/tech-decisions/

    • Use the ADR template format (Context, Options, Decision, Rationale, Consequences)
    • Add frontmatter: type: decision, date, status: accepted, tags
  2. Debugging breakthroughs — Save as a debug journal entry in $VAULT_PATH/03_Resources/debugging-journal/

    • Use the Five Whys format (Symptoms, Root Cause, Fix, Prevention)
    • Add frontmatter: type: debug, date, severity, resolved: true, tags
  3. Reusable patterns — Save as a resource in $VAULT_PATH/03_Resources/patterns/

    • Include: pattern name, when to use, example code, gotchas
    • Add frontmatter: type: pattern, date, language, tags
  4. Project milestones — Update existing project notes in $VAULT_PATH/01_Projects/

    • Append to the project's progress log
    • Link to related decision records or debug journals

Skip criteria:

  • Routine file edits with no architectural significance
  • Test runs that passed without issues
  • Simple typo fixes or formatting changes
  • Anything already captured in the vault

For each promoted observation:

  • Create a properly formatted Obsidian note using the appropriate template
  • Add [[links]] to related existing notes where applicable
  • Add appropriate tags for discoverability
  • Commit the new notes to Git

Output: Summary of what was promoted, what was skipped, and why.

Changes

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.

  1. 12d ago First seen · 43 lines · 24 tokens per session scan A da25e60560c8

Subscribe to this mod's changes

promote-to-vault is a skill published in the GitHub repository Shashank2577/hesoyam-for-claude-code (11 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 483 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-31.