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 davidvkimball/obsidian-dev-skills --skill obsidian-opsgit clone --depth 1 https://github.com/davidvkimball/obsidian-dev-skillsWrote 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/davidvkimball/obsidian-dev-skills/obsidian-ops)<a href="https://agentmods.dev/skills/davidvkimball/obsidian-dev-skills/obsidian-ops"><img src="https://agentmods.dev/badge/skills/davidvkimball/obsidian-dev-skills/obsidian-ops/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/davidvkimball/obsidian-dev-skills/obsidian-ops"><img src="https://agentmods.dev/badge/skills/davidvkimball/obsidian-dev-skills/obsidian-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.00413 |
| Opus 5 | $0.00019 | $0.00206 |
| Sonnet 5 | $0.00008 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
obsidian-ops 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 11d 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 Operations Skill
This skill covers the operational aspects of maintaining an Obsidian project, including build workflows, sync procedures, and release management.
Purpose
To ensure reliable builds, consistent reference materials, and safe release processes while strictly following project policies.
Scope
This skill covers:
- Build and lint workflows
- Syncing reference documentation from external sources
- Version management and release preparation
- Build and environment troubleshooting
Core Rules
- NEVER perform automatic git operations: AI agents must never execute
git commit,git push, or any command that automatically stages or commits changes without explicit user approval for each step. - Verify Build: Always run a build/lint after significant changes to ensure compatibility.
- Sync Status: Keep
sync-status.jsonupdated when updating reference materials.
Bundled Resources
references/build-workflow.md: Standard build and development commands.references/release-readiness.md: Checklist for ensuring a project is ready for release.references/scorecard-compliance.md: Map of Obsidian community plugin scorecard signals to concrete fixes (vulnerability overrides, attestation workflow, CSS dedup, obsidianmd rules).references/contributing-template.md: Portable CONTRIBUTING.md template for the scorecard hygiene check.references/security-privacy.md: Developer policies, mandatory disclosures, and dependency vulnerability hygiene viapnpm.overrides.references/sync-procedure.md: How to pull updates from reference repositories.references/versioning-releases.md: Workflow for versioning and GitHub releases, including the build-provenance attestation pattern.references/troubleshooting.md: Common issues and their resolutions.references/quick-reference.md: One-page cheat sheet for common operations.
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/build-workflow.md 2.8 KB
- references/contributing-template.md 4.1 KB
- references/performance.md 486 B
- references/quick-reference.md 5.2 KB
- references/quick-sync-guide.md 5.2 KB
- references/release-readiness.md 9.8 KB
- references/scorecard-compliance.md 25 KB
- references/security-privacy.md 4.7 KB
- references/summarize-commands.md 4.0 KB
- references/sync-procedure.md 14 KB
- references/testing.md 590 B
- references/troubleshooting.md 3.7 KB
- references/versioning-releases.md 6.0 KB
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.
- 11d ago First seen · 39 lines · 38 tokens per session scan A 53d7871245ac
obsidian-ops is a skill published in the GitHub repository davidvkimball/obsidian-dev-skills (52 stars, last pushed 14d ago), licensed MIT. It adds 38 tokens to every session and 413 once invoked, about $0.0002 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-30.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
skillshare-release
End-to-end release workflow for skillshare. Runs tests, generates changelog (via /changelog), optionally writes local RELEASENOTES, updates version numbers, commits, and drafts announcements. Use when the user says "release", "prepare release", "cut a release", "release v0.19", or any request to publish a new version.…
release-checks
Portable release checklist skill for the Cursor packaged example.
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.