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 authoring-issues-prsgit 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/authoring-issues-prs)<a href="https://agentmods.dev/skills/pvliesdonk/markdown-vault-mcp/authoring-issues-prs"><img src="https://agentmods.dev/badge/skills/pvliesdonk/markdown-vault-mcp/authoring-issues-prs/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/authoring-issues-prs"><img src="https://agentmods.dev/badge/skills/pvliesdonk/markdown-vault-mcp/authoring-issues-prs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 12 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00086 | $0.01493 |
| Opus 5 | $0.00043 | $0.00746 |
| Sonnet 5 | $0.00017 | $0.00299 |
| Haiku 4.5 | $0.00009 | $0.00149 |
Grade A, and why
authoring-issues-prs 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 10d 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
2 near-identical copies found in the catalogue:
- authoring-issues-prs — 100% identical, 0 lines differ
- authoring-issues-prs — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring issues and pull requests
CONTRIBUTING.md at the repository root is the single source for the rules:
issue voice, uncertainty markers, one-issue-one-problem, PR discipline, and
the three-tier routing. This skill adds only what a document cannot — the
trigger, the order of operations, and the API mechanics for the steps issue
forms cannot perform. It deliberately does not restate the rules; a second
copy would drift from the file silently.
Procedure
1. Read CONTRIBUTING.md — now, not from memory
Read CONTRIBUTING.md (repository root) before drafting a single sentence,
even if you believe you remember it. You are about to apply these sections,
and their exact wording matters:
- "Observation, not work order" and "The uncertainty rule" — issue voice
and the
[verified: how]/[unverified]markers. - "One issue, one observed problem" and the "Remove before posting" table — run your draft through the table before submitting.
- "Pull requests" — no orphan PRs, the deliberately-does-not section.
- "Where to send fixes" — the routing walked in step 2.
If anything in this skill appears to conflict with CONTRIBUTING.md, the
file wins.
2. Route before writing
Decide the repo first, then write for that repo. The test: which file would a fix change?
- Anything you'd change in
fastmcp_pvl_core→ library: file onpvliesdonk/fastmcp-pvl-core. - A template-owned file — workflows,
Dockerfile, theserver.pyskeleton, anythingcopier updatere-renders — → template: file onpvliesdonk/fastmcp-server-template. - Anything inside a
DOMAIN-*/CONFIG-*/PROJECT-*sentinel block, ortools.py/resources.py/prompts.py/domain.py/tests/→ domain: file on this repository.
CONTRIBUTING.md's "Where to send fixes" defines these tiers with the
post-merge propagation for each. When the tier is genuinely unclear, say so
in the issue with an [unverified] marker instead of guessing silently.
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.
- 10d ago First seen · 143 lines · 86 tokens per session scan A 539b6aab8e11
authoring-issues-prs is a skill published in the GitHub repository pvliesdonk/markdown-vault-mcp (32 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 1,493 once invoked, about $0.0004 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
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]…
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, …).
tasks
View and manage the task stack and processing queue. Shows pending work, active tasks, completed items, and queue state. Triggers on "/tasks", "show tasks", "what's pending", "task list", "queue status".
hyalo-changelog
Maintain Keep a Changelog files with Hyalo's changelog profile and add/release commands.
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.
gh-sync
Sync GitHub issues and pull requests into the Distillery knowledge base as searchable, linkable entries.