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.
git clone --depth 1 https://github.com/gapmiss/obsidian-plugin-skillWrote 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/commands/gapmiss/obsidian-plugin-skill/create-plugin)<a href="https://agentmods.dev/commands/gapmiss/obsidian-plugin-skill/create-plugin"><img src="https://agentmods.dev/badge/commands/gapmiss/obsidian-plugin-skill/create-plugin/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/commands/gapmiss/obsidian-plugin-skill/create-plugin"><img src="https://agentmods.dev/badge/commands/gapmiss/obsidian-plugin-skill/create-plugin.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.00013 | $0.00391 |
| Opus 5.5 | $0.00005 | $0.00156 |
| Sonnet 5.5 | $0.00003 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
create-plugin 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
You are helping the user create a new Obsidian plugin. Follow these steps:
Setup Options
Present the user with two options:
-
Automated Setup (Recommended): Use the interactive boilerplate generator script
- Run:
node /path/to/obsidian-plugin-skill/tools/create-plugin.js - This creates a minimal, best-practice plugin structure automatically
- Detects existing projects and only adds missing files
- All generated code follows the Obsidian Plugin Development Skill guidelines
- Run:
-
Manual Setup: Guide the user through creating files step-by-step
- Walk through each required file
- Explain what each file does
- Provide code that follows best practices from the skill
After Setup
Once the boilerplate is created (either way):
-
Verify all files follow the skill's best practices:
- No sample code (MyPlugin, SampleModal, etc.)
- Proper use of registerEvent() for cleanup
- Sentence case in UI text
- Obsidian CSS variables in styles
- Accessibility-ready templates
-
Help customize the plugin:
- Ask what the plugin will do
- Suggest appropriate API usage patterns
- Reference specific sections of the skill as needed
-
Guide through initial development:
- Setting up the dev environment
- Testing in Obsidian
- Common next steps
Important Reminders
- Always apply the Obsidian Plugin Development Skill guidelines
- Ensure accessibility from the start (keyboard navigation, ARIA labels, focus indicators)
- Use TypeScript best practices (instanceof, not type casting)
- Follow memory management rules (proper event registration)
- Use Obsidian CSS variables for theming
Ask the user which setup option they prefer, then proceed accordingly.
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 · 52 lines · 13 tokens per session scan A 55325ba8342f
create-plugin is a command published in the GitHub repository gapmiss/obsidian-plugin-skill (192 stars, last pushed 6d ago), licensed MIT. It adds 13 tokens to every session and 391 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-08-30.
Other commands, from other repositories
token-cost-tracker
Estimate, log, and report token usage using runtime-supplied billing rates; never rely on embedded model prices.
wiki-lint
Run a health check on the wiki. Invoke with /wiki-lint or "lint the wiki".
daily-okr
Run a daily knowledge compound loop (7 KR). Invoke with /daily-okr or "start my daily review".
session-learn
Extract knowledge from the current session. Invoke with /session-learn or "extract this session".
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.