compound

compound is a skill for Claude Code from thoreinstein/obsidian-rag. It costs 42 tokens per session (413 once invoked), scanned A, a copy of compound, MIT.

A process for finding ideas repeated across several project knowledge folders and combining them into a general engineering note.

In plain words
What is it for?
Use it to discover shared patterns, draft a synthesized note with links to its source notes, and publish it to the global Engineering folder after approval.
Why use it?
It turns project-specific lessons into reusable guidance instead of leaving similar insights scattered across separate notes.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the obsidian-rag plugin — 13 skills, 2 agents shipped together

Good fit Use it to discover shared patterns, draft a synthesized note with links to its source notes, and publish it to the global Engineering folder after approval.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/thoreinstein/obsidian-rag/compound
Install

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.

Any agent
npx skills add thoreinstein/obsidian-rag --skill compound
Clone the repo
git clone --depth 1 https://github.com/thoreinstein/obsidian-rag

Made for: Claude Code.

Or install obsidian-rag, the plugin that ships this one along with the rest of its 13 skills, 2 agents.

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 compound

README.md
[![agentmods](https://agentmods.dev/badge/skills/thoreinstein/obsidian-rag/compound/github.svg)](https://agentmods.dev/skills/thoreinstein/obsidian-rag/compound)
Your own site
<a href="https://agentmods.dev/skills/thoreinstein/obsidian-rag/compound"><img src="https://agentmods.dev/badge/skills/thoreinstein/obsidian-rag/compound/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 compound

Your own site · 80×15
<a href="https://agentmods.dev/skills/thoreinstein/obsidian-rag/compound"><img src="https://agentmods.dev/badge/skills/thoreinstein/obsidian-rag/compound.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 413 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 100% copy Near-identical to another mod 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.00042 $0.00413
Opus 5.5 $0.00017 $0.00165
Sonnet 5.5 $0.00008 $0.00083
Haiku 4.5 $0.00004 $0.00041

Measured 1mo ago against content hash d5e3b1e05af0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

Origin

This is a copy

100% identical to compound — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/compound/SKILL.md · 46 lines

What it actually says

Compound Knowledge Promotion

Identify knowledge that has crystallized across multiple projects and promote it to a global Engineering/ note.

Workflow

  1. Scan project knowledge dirs — Call obsidian_list_notes with subfolder: "working". Filter results to paths matching working/*/knowledge/*.md.

  2. Semantic clustering — For each knowledge note path, call obsidian_rag_query with the note filename (without extension) as query, limit: 8. Track which notes appear in results from 2+ different projects — these are candidates.

  3. Read candidates — Call obsidian_read_note on shortlisted files. Look for shared definitions, patterns, or insights worth generalizing.

  4. Draft global note — Compose a new Engineering/<ConceptName>.md with:

    • Frontmatter: type: concept, created: <today>
    • Synthesized body (not copy-paste — rewrite for clarity)
    • ## Source Notes section with [[wikilinks]] back to originating notes
  5. Show draft to user — Present the proposed note content and path before creating. Ask for confirmation.

  6. Create on approval — Call obsidian_create_note with the approved content.

  7. Report cross-links — List which project knowledge notes should now add [[ConceptName]] to avoid re-discovering this knowledge next time.

Arguments

Optional topic hint: /compound authentication patterns

Tips

  • If obsidian_rag_query returns no results, suggest running /index first
  • If no notes appear in 2+ projects, report that and suggest manual promotion
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. 1mo ago First seen · 46 lines · 42 tokens per session scan A d5e3b1e05af0

Subscribe to this mod's changes

compound is a skill published in the GitHub repository thoreinstein/obsidian-rag (2 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 413 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to compound, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

acm-handoff

Use when resuming work from a previous session that reached context threshold, or when a handoff summary exists. Reads handoff state and markdown to restore context, todos, and continue seamlessly.

povvo/claudikins-automatic-context-manager · 43 tokens

acm-config

Use when the user wants to customize Claudikins Automatic Context Manager behavior, configure trigger threshold, snooze duration, summary length, or runs '/acm:config'. Interactively asks questions and saves preferences to config file.

povvo/claudikins-automatic-context-manager · 50 tokens

whats-up

Fetch recent activity from Autographical — what the user and their AI agents have been working on. Use when starting a session, when the user mentions recent activity, when the user alludes to what they were doing or looking at, or picking up where they left off. Also use when the conversation feels like a topic…

autographical/claude-code-plugins · 75 tokens

user-profile

Use to create or update the user's anchor profile — a single private file (/bettersense-work-reflections/profile.md) that captures who the user is, what they do, what context other skills need to know about them. Read automatically by other skills in the bundle when present, so the user doesn't re-explain themselves…

shwetank/bettersense · 131 tokens

career-retro

Use for a periodic (quarterly / annual) career retrospective across the ENTIRE bettersense memory — producing a longitudinal self-assessment with cited growth deltas since the last retro and the honest gaps to work on next. Trigger phrases include "run my career retro", "where am I in my career", "annual…

shwetank/bettersense · 166 tokens

doctor

Use to health-check the user's bettersense memory directory — validate the file layout, catch problems before they cost data, and set up backups. Trigger phrases include "run bettersense doctor", "check my reflection files", "is my bettersense data okay", "something seems off with my stakeholder files", "back up my…

shwetank/bettersense · 0 tokens