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 pvliesdonk/markdown-vault-mcp --skill repository-protectiongit clone --depth 1 https://github.com/pvliesdonk/markdown-vault-mcpWrote 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/pvliesdonk/markdown-vault-mcp/repository-protection)<a href="https://agentmods.dev/skills/pvliesdonk/markdown-vault-mcp/repository-protection"><img src="https://agentmods.dev/badge/skills/pvliesdonk/markdown-vault-mcp/repository-protection/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/pvliesdonk/markdown-vault-mcp/repository-protection"><img src="https://agentmods.dev/badge/skills/pvliesdonk/markdown-vault-mcp/repository-protection.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.00031 | $0.00436 |
| Opus 5 | $0.00015 | $0.00218 |
| Sonnet 5 | $0.00006 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
repository-protection 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- repository-protection — 100% identical, 0 lines differ
What it actually says
Repository Protection
Repository protection (rulesets)
.github/rulesets/*.json are the source of truth for this repository's branch and tag rulesets — required PRs + the CI Success check on main and release/*, deletion/force-push protection for v* tags — and bootstrap.yml applies them (upsert by name) on pushes touching those files and on manual dispatch. Never adjust protection in the GitHub UI: the next bootstrap run resets it to the checked-in state. Change the JSON files instead. The release pipeline's RELEASE_TOKEN (a repository admin's PAT) bypasses these rules by design via the admin-role bypass entry — its remaining jobs are creating the vX.Y.Z tag + GitHub release after a release PR merges (the v* tag ruleset applies) and opening the release/notes/port PRs whose CI must run; direct release-commit and merge-back pushes to protected branches are gone with PSR. Posture and bypass model: docs/deployment/repository-protection.md.
A check that is not a job in ci.yml cannot join the CI Success aggregate — needs: only reaches jobs in the same workflow — so a domain workflow this project adds is advisory until its context is required outright. Declare it in the extra_required_checks answer instead, which renders into both branch rulesets alongside CI Success, rather than editing ci.yml or the ruleset files by hand. Every context listed there must report on every PR to a protected branch: a paths: filter or a false job-level if: reports nothing, and the merge then waits forever for a check that is not coming. Details and the workflow shape that avoids it: docs/deployment/repository-protection.md.
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.
- 12d ago First seen · 16 lines · 31 tokens per session scan A 4bfc3a78ef41
repository-protection is a skill published in the GitHub repository pvliesdonk/markdown-vault-mcp (32 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 436 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
solomd
Read, search, edit, and version-control any folder of Markdown notes via the SoloMD MCP server. 13 tools including AutoGit per-note history, semantic search, and write-with-sandbox via an accept/reject branch. Includes 11 starter agent recipes (weekly review, todo extract, link suggester, …).
hyalo-changelog
Maintain Keep a Changelog files with Hyalo's changelog profile and add/release commands.
gh-sync
Sync GitHub issues and pull requests into the Distillery knowledge base as searchable, linkable entries.
mnemonic
Search local indexed markdown knowledge bases. Use when the user asks to find notes, dig up a concept from personal docs, cross-reference ideas across wikis, or answer from indexed local files. Triggers on "look up in notes", "search my docs", "what did I write about", "find in my vault", "check my index", "retrieve…
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
github
Use when interacting with GitHub repositories, authentication, remotes, pushes, or repository creation through the GitHub CLI and related git workflows.