Borrowing it
Nothing to install: this file belongs to psenger/obsidian-markdown-lint-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/psenger/obsidian-markdown-lint-mcp-server/main/.claude/skills/conventions/SKILL.mdgit clone --depth 1 https://github.com/psenger/obsidian-markdown-lint-mcp-serverWrote 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/psenger/obsidian-markdown-lint-mcp-server/conventions)<a href="https://agentmods.dev/skills/psenger/obsidian-markdown-lint-mcp-server/conventions"><img src="https://agentmods.dev/badge/skills/psenger/obsidian-markdown-lint-mcp-server/conventions/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/psenger/obsidian-markdown-lint-mcp-server/conventions"><img src="https://agentmods.dev/badge/skills/psenger/obsidian-markdown-lint-mcp-server/conventions.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.00120 | $0.00952 |
| Opus 5 | $0.00060 | $0.00476 |
| Sonnet 5 | $0.00024 | $0.00190 |
| Haiku 4.5 | $0.00012 | $0.00095 |
Grade A, and why
conventions 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventions: obsidian-markdown-lint-mcp-server
Commit messages
Format: type(scope): subject
- Subject: imperative mood, lowercase, no trailing period, 72 characters or fewer
- Scope: the code area touched (
tools,lint,validate,mermaid,server,lib,schemas) or a repo area (ci,docker,deps,readme,release) - Body: optional; explain why, not what; wrap at 72 chars
- Footer:
Closes #NorFixes #Nfor GitHub issues;BREAKING CHANGE: <desc>for breaking changes
Do not add Co-Authored-By trailers.
Types
| Type | When |
|---|---|
feat |
New tool, or a new capability in an existing tool |
fix |
Bug fix in tool behaviour or output |
chore |
Release commits, tooling, deps, config; no behaviour change |
docs |
README, CHANGELOG, CONTRIBUTING only |
refactor |
Code restructure with no behaviour change |
test |
Unit, eval, or snapshot test changes |
Release commit, always exactly:
chore(release): cut vX.Y.Z release
Examples
feat(mermaid): add per-document theme override
fix(lint): preserve trailing newline in fixed_content
Closes #12
Branch names
Pattern: type/issue-number-short-description
feature/14-mermaid-theme-option
fix/23-lint-trailing-newline
chore/release-v0-2-0
feature/for new tools or capabilitiesfix/for bug fixeschore/for release and tooling work- Always include the issue number when one exists
- 2 to 4 words, hyphenated, no version dots (use dashes)
Pull requests
Title: same format as a commit, type(scope): subject
Fill in the repo PR template at .github/PULL_REQUEST_TEMPLATE.md. It expects: what and why, how, and the checklist (build, test, eval, snapshot, audit, tests added, docs updated). Always link the issue with Closes #N.
What ships with it
1 file 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.
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 · 117 lines · 120 tokens per session scan A 3ff9fc217164
conventions is a skill published in the GitHub repository psenger/obsidian-markdown-lint-mcp-server (2 stars, last pushed yesterday), licensed MIT. It adds 120 tokens to every session and 952 once invoked, about $0.0006 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
git
Open Harness git workflow: issues, branches, commits, PR titles/bodies, changelog discipline, worktrees, branch catch-up, stacked PRs, releases, and post-push CI checks. TRIGGER when: any chat mentions git, GitHub, branches, commits, pushes, pulls, PRs, issues, worktrees, merge conflicts, dirty workspaces, changelog…
github-ops
Fast GitHub operations via the gh CLI. Use when the user mentions GitHub issues, PRs, repos, actions, releases, creating or triaging issues, opening or reviewing pull requests, managing branches, inspecting repo state, or checking CI. Works on any repo the operator's gh CLI is authenticated against.
git-workflow
Branch naming, commit message format, and PR conventions. Use when making git commits or creating PRs.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
re0-git
Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, so git log alone tells the story. User-invoked: run it after a commit.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.