Borrowing it
Nothing to install: this file belongs to pvliesdonk/paperless-mcp. 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/pvliesdonk/paperless-mcp/main/.agents/skills/repository-protection/SKILL.mdgit clone --depth 1 https://github.com/pvliesdonk/paperless-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/paperless-mcp/repository-protection)<a href="https://agentmods.dev/skills/pvliesdonk/paperless-mcp/repository-protection"><img src="https://agentmods.dev/badge/skills/pvliesdonk/paperless-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/paperless-mcp/repository-protection"><img src="https://agentmods.dev/badge/skills/pvliesdonk/paperless-mcp/repository-protection.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.00031 | $0.00476 |
| Opus 5.5 | $0.00012 | $0.00190 |
| Sonnet 5.5 | $0.00006 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00048 |
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 25d 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.
This is a copy
100% identical to repository-protection — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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, release/* and integration/* (not strict: a PR need not be up to date with its base to merge), 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 the main and release/* rulesets alongside CI Success (integration/* requires CI Success alone), 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.
- 25d ago Changed 71320a7e8bd2
- 1mo ago First seen · 16 lines · 31 tokens per session scan A 4bfc3a78ef41
repository-protection is a skill published in the GitHub repository pvliesdonk/paperless-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 476 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to repository-protection, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
report-issue
File a bug or feature request against this repository (cyanheads/git-mcp-server) using the gh CLI. Use for tool logic bugs, git provider misbehavior, transport issues, auth/config problems, or new feature proposals.
triaging-incidents
Creating, triaging, updating, and analyzing ServiceNow incidents, including trend reports. Assess severity, check affected CIs, find related incidents, and recommend assignments. Use when the user mentions incidents, INC numbers, outages, service disruptions, ticket creation, triage, priority, severity, ITSM…
reviewing-update-sets
Reviewing, analyzing, and comparing ServiceNow update sets before promotion, singly or in batches. Shows changes, risks, dependencies, and conflicts. Use when the user mentions update sets, customizations, promotion, code review, change tracking, pre-deployment review, sysupdatexml, customer updates, 'what changed in…
assessing-change-impact
Assessing what a ServiceNow change request touched and what followed it: affected CIs, other changes on the same CIs in an overlapping window, and incidents on those CIs after the change, without trusting hidden incident-to-change links. Use this skill whenever the user asks whether a change (a CHG number) caused or…
reviewing-sla-definitions
Reviewing ServiceNow SLA, OLA and underpinning-contract definitions and how they perform: breach rates per definition, overlapping or duplicated definitions on the same table and target, and definitions that never attach. Use when the user asks about SLA breaches by definition, too many SLAs, duplicate or conflicting…