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 CodeInfinity1/Stram --skill obsidian-notesgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/obsidian-notes)<a href="https://agentmods.dev/skills/codeinfinity1/stram/obsidian-notes"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/obsidian-notes/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/codeinfinity1/stram/obsidian-notes"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/obsidian-notes.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.00031 | $0.00373 |
| Opus 5.5 | $0.00012 | $0.00149 |
| Sonnet 5.5 | $0.00006 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
obsidian-notes 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.
What it actually says
Obsidian Notes
Purpose
Support local markdown-based knowledge work, including Obsidian vaults, without requiring a plugin. Stram can search/read/write notes inside allowed workspace roots.
When To Use
Use for markdown notes, vault search, daily notes, backlinks/plans, knowledge capture, and note cleanup.
Inputs And Evidence
- Vault path, note title/path, tags, links, source evidence, and desired output.
- Existing note contents and naming conventions.
Tool Map
search_workspacelist_filesread_filewrite_notememory_writeknowledge-base-builder
Workflow
- Confirm vault/path boundary.
- Search existing notes before creating duplicates.
- Preserve user naming, tags, and link style.
- Write concise notes with source evidence.
- Use memory only for durable assistant context, not every note.
- Verify created note path or updated content.
Native Implementation Boundaries
- Use Stram file/note tools.
- Do not import external reference Obsidian scripts.
- Do not depend on Obsidian app plugins unless a native adapter exists.
Safety And Approval
- Vaults may contain private personal data.
- Avoid broad rewrites.
- Do not expose notes to external channels without approval.
Verification
- Confirm file path and content.
- Check for duplicate note titles when relevant.
- Report if path is outside allowed roots.
Failure Modes
- Creating duplicate scattered notes.
- Breaking backlink conventions.
- Mixing memory records with vault notes.
References
- Shortlist item:
obsidian-notes.
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.
- 1mo ago First seen · 66 lines · 31 tokens per session scan A 62f57758fc1b
obsidian-notes is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 373 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
lighting-report-extract
Check reported lighting quantities and results in supplied simulation PDFs without adding repeated calculation surfaces. Use for scoped luminaire inventories and illuminance results; not simulation or compliance.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
container-debugging
Diagnose reported container build, startup, network, permission and resource failures. Use when an image or Compose service fails; reproduce against the final image/config and avoid data-destroying cleanup as a workaround.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…