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/config-contract/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/config-contract)<a href="https://agentmods.dev/skills/pvliesdonk/paperless-mcp/config-contract"><img src="https://agentmods.dev/badge/skills/pvliesdonk/paperless-mcp/config-contract/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/config-contract"><img src="https://agentmods.dev/badge/skills/pvliesdonk/paperless-mcp/config-contract.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.00039 | $0.02460 |
| Opus 5.5 | $0.00016 | $0.00984 |
| Sonnet 5.5 | $0.00008 | $0.00492 |
| Haiku 4.5 | $0.00004 | $0.00246 |
Grade C, and why
config-contract scanned grade C with 1 finding 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
Domain configuration composes `fastmcp_pvl_core.ServerConfig` inside your domain config class (see `src/paperless_mcp/config.py`). Add domain fields between the `CONFIG-FIELDS-START` / `CONFIG-FIELDS-END` sentinels, popu This is a copy
86% identical to config-contract — 6 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Config Contract
Config & Customization Contract
Domain configuration composes fastmcp_pvl_core.ServerConfig inside your domain config class (see src/paperless_mcp/config.py). Add domain fields between the CONFIG-FIELDS-START / CONFIG-FIELDS-END sentinels, populate them in from_env between the CONFIG-FROM-ENV-START / CONFIG-FROM-ENV-END sentinels, and enforce their invariants in __post_init__ between the CONFIG-VALIDATE-START / CONFIG-VALIDATE-END sentinels. Validation belongs in __post_init__ rather than from_env because it then also covers a direct ProjectConfig(field=...); env_float / env_int bounds check only the env-sourced value, are inclusive-only, and cannot express cross-field rules. A variable that must be set is read with env(_ENV_PREFIX, "NAME", required=True) in from_env — it refuses at startup with a ConfigurationError and the generated docs mark it required — and returned from config_contract_env in tests/conftest.py. __post_init__ checks values and rejects them with ConfigurationError (already imported in config.py), never ValueError: serve reports only ConfigurationError as its one-line ERROR: configuration error: … exit. Never refuse an empty required field in __post_init__. The dataclass is frozen — read fields, don't assign (use object.__setattr__ if a field must be normalised). Never inherit from ServerConfig; always compose.
Env var prefix is PAPERLESS_MCP_ — all env reads go through fastmcp_pvl_core.env(_ENV_PREFIX, "SUFFIX", default) so naming stays consistent.
- Domain CLI subcommands go in the
# DOMAIN-COMMANDS-START/-ENDblock incli.py(likeCONFIG-FIELDSinconfig.py). Register them as@app.command()and use function-local imports for domain modules. The block is preserved acrosscopier update.
Config wizard
docs/javascripts/config-wizard/wizard-spec.json drives the guided-setup page. It is generated, produced by scripts/gen_config_surface.py on every copier copy/copier update and re-verified by scripts/gen_config_surface.py --check in CI — never hand-edit it. The runtime (wizard.js, generators.js, wizard-spec-schema.json, the generic tests) is template-owned and re-rendered the same way it always was.
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 scan A → C c39ab260614b
- 1mo ago First seen · 62 lines · 39 tokens per session scan A ca7d2bf4bb26
config-contract is a skill published in the GitHub repository pvliesdonk/paperless-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 2,460 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (tells the agent never to refuse). It is 86% identical to config-contract, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
servicenow-cmdb
Auditing the CMDB as a data model: CI class hierarchy, raw relationships, CMDB health scorecards, data quality (duplicates, orphans, staleness, missing fields) and CSDM 5 conformance. Use when the user mentions CMDB health, CMDB audit, data quality, duplicates, orphaned or stale CIs, CI classes, relationships in…
exploring-tables
Exploring any ServiceNow table: schema, field types, sample records, relationships, data patterns, a record's history (work notes, comments, field changes), and what touches a table or field (business rules, client scripts, UI policies, ACLs, script includes). Use when the user mentions tables, schemas, fields, data…
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…
analyzing-access
Reviewing who holds which ServiceNow roles and explaining access denials. Lists admin and securityadmin holders, roles granted directly instead of through groups, roles left on inactive or long-absent users, and diagnoses 401/403 errors, empty results and missing fields. Joins users, groups and roles through…
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…