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 JeanDiable/obsidian-claude --skill archivegit clone --depth 1 https://github.com/JeanDiable/obsidian-claudeWrote 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/jeandiable/obsidian-claude/archive)<a href="https://agentmods.dev/skills/jeandiable/obsidian-claude/archive"><img src="https://agentmods.dev/badge/skills/jeandiable/obsidian-claude/archive/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/jeandiable/obsidian-claude/archive"><img src="https://agentmods.dev/badge/skills/jeandiable/obsidian-claude/archive.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.00021 | $0.00467 |
| Opus 5 | $0.00010 | $0.00234 |
| Sonnet 5 | $0.00004 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
archive 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 10d 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
Archive
Check all projects for completion status, generate wrap-up summaries, and archive finished work.
Vault Path
/Library/Mobile Documents/iCloudmd~obsidian/Documents/My_note
Workflow
Step 1: Scan Projects
-
List all items in
20_Projects/ -
For each project, read frontmatter and content to determine:
- Completed:
completed: truein frontmatter, or content clearly indicates finished - Active: Clear ongoing work, recent modifications
- Stale: No updates in 30+ days, unclear status
- Unknown: No metadata, can't determine
- Completed:
-
Present status report:
Projects: N total Completed (ready to archive): X Active: Y Stale (needs review): Z Unknown status: W
Step 2: User Review
For stale and unknown projects, ask user one by one:
- Archive it? (completed)
- Keep active? (still working on it)
- Delete? (abandoned, not worth keeping)
Step 3: Archive Completed Projects
For each project to archive:
- Set
completed: trueand updatemodifieddate in frontmatter - Generate a wrap-up section at the end of the file:
## Archive Summary - **Archived**: YYYY-MM-DD - **Duration**: Started YYYY-MM-DD, ended YYYY-MM-DD - **Outcome**: [Brief summary of what was accomplished] - **Key learnings**: [What was learned] - Move to
80_Archive/ - Update any files that link to this project (wikilinks still work regardless of folder)
Step 4: Report
List all actions taken.
Important Rules
- Never auto-archive without user confirmation
- Preserve all content — archiving is moving, not deleting
- Update the modified date when archiving
- Wikilinks to archived projects still work (Obsidian resolves by filename)
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.
- 10d ago First seen · 65 lines · 21 tokens per session scan A dd5d175324ef
archive is a skill published in the GitHub repository JeanDiable/obsidian-claude (2 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 467 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.