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 lyupro/skillforge-mcp --skill obsidian-resumegit clone --depth 1 https://github.com/lyupro/skillforge-mcpWrote 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/lyupro/skillforge-mcp/obsidian-resume)<a href="https://agentmods.dev/skills/lyupro/skillforge-mcp/obsidian-resume"><img src="https://agentmods.dev/badge/skills/lyupro/skillforge-mcp/obsidian-resume/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/lyupro/skillforge-mcp/obsidian-resume"><img src="https://agentmods.dev/badge/skills/lyupro/skillforge-mcp/obsidian-resume.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.00019 | $0.00436 |
| Opus 5 | $0.00010 | $0.00218 |
| Sonnet 5 | $0.00004 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
obsidian-resume 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 9d 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.
What it actually says
You are picking up a session previously summarised in an Obsidian daily-log "Session Handoff" block. The user input contains the full Session Handoff text (the block produced by the /obsidian:handoff skill, typically ending with ### Memory Flush or another section break).
Your task:
- Restate the working state in one short paragraph — what was being worked on, which branch, last commit, uncommitted state.
- List the active TODOs verbatim from the handoff's "Active TODOs" or "Next steps" section. Preserve checkbox state (
[x]/[ ]). - Surface open questions the previous session left unresolved. Quote each one as the previous session phrased it.
- Identify the next concrete action — the first item from the "Next steps" list that is actionable now (not blocked on user input).
- Ask one clarifying question — the most useful one given the open questions. If everything is unambiguous, ask "Ready to start with ?".
Output format (Markdown):
## Picking up where we left off
<paragraph summarising state>
## Active TODOs
- [x] / [ ] ...
- ...
## Open questions from the previous session
- ...
## Next concrete action
<one sentence>
## My question
<the one clarifying question>
Constraints:
- Quote the handoff verbatim where possible. Do not paraphrase commits, file paths, or commit SHAs.
- If the handoff is incomplete (missing "Active TODOs" or "Next steps"), say so explicitly in the corresponding section — do not fabricate items.
- Convert any relative dates from the handoff ("yesterday", "this morning") to absolute dates if a header date is available; otherwise leave them as-is and note the ambiguity.
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.
- 9d ago First seen · 48 lines · 19 tokens per session scan A 4506f2728635
obsidian-resume is a skill published in the GitHub repository lyupro/skillforge-mcp (2 stars, last pushed 25d ago), licensed MIT. It adds 19 tokens to every session and 436 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.
Other skills, from other repositories
wiki-switch
Switch between multiple Obsidian wiki vault profiles. Use this skill when the user says "/wiki-switch NAME", "switch to my work wiki", "switch vault", "change wiki", "which wiki am I on", "list my wikis", "show my vaults", "create a new vault config", or "add a new wiki profile". The skill manages named config files…
knowledge-base-management
A lifecycle system for managing an Obsidian knowledge base, which is a folder of linked notes. It organizes raw material, AI-maintained wiki pages, and generated views into separate layers.
setup-brain
Set up or upgrade an AI-powered Obsidian vault. Interviews you, builds your vault structure (or works with what you already have), creates your CLAUDE.md memory file, installs tools, and gets you journaling — all in one conversation. Also has a repair/upgrade path for existing users.
second-brain-mapping
Use when the user wants to map or remap their second brain, refresh the vault's queryable metadata index, extract structured frontmatter from typed notes (books, meetings, people, journals, goals), fill wikilink gaps, or surface cross-type insights and patterns no single file shows. Triggers: /second-brain-mapping…
evolve
Use when many related hardened instincts (high-confidence feedback/discovery memories) have piled up in one domain, when the user runs /evolve or asks to promote, cluster, graduate, or consolidate accumulated instincts into a Command, Skill, or Agent, or when files in Instinct Proposals need review. Part of the…
chief-of-staff
Personal Chief of Staff system for ADHD-ish operators. Vault-based, loop-driven, nervous-system-aware. Built and lived-in across daily sessions on real consulting, content, and long-running personal work.