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/researching-references/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/researching-references)<a href="https://agentmods.dev/skills/pvliesdonk/paperless-mcp/researching-references"><img src="https://agentmods.dev/badge/skills/pvliesdonk/paperless-mcp/researching-references/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/researching-references"><img src="https://agentmods.dev/badge/skills/pvliesdonk/paperless-mcp/researching-references.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.00099 | $0.02456 |
| Opus 5.5 | $0.00040 | $0.00982 |
| Sonnet 5.5 | $0.00020 | $0.00491 |
| Haiku 4.5 | $0.00010 | $0.00246 |
Grade A, and why
researching-references 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 1mo 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
95% identical to researching-references — 0 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Researching references
A reference is a page under docs/design/reference/ that records how
something outside this repository behaves: the rules of a markdown
dialect, what a git remote refuses and how it says so, the quirks of a file
format or a vendor API. It exists because the alternative is worse in a
specific way: an agent that meets such a question mid-task answers it from
parametric memory, which is consistently incomplete, outdated, or wrong in
the details that matter, and the design doc only ever records the facets that
already broke. Six issues about one rule set, each rediscovering one facet,
is the failure this skill exists to stop.
A reference is not the design doc. docs/design/ says what this project
does and why; a reference says what the world does, with the evidence. When
the two disagree on purpose, the reference records the world and links to the
design decision that departs from it.
When to write or refresh one
- A bug or feature turns on an external behaviour and no reference under
docs/design/reference/covers it. Write one before fixing: the fix is then a consequence of the reference, not a guess the reference later contradicts. - A reference exists but its
stale_afterdate has passed, itssubject_versionis no longer what the project targets, or itsstatusisdeprecatedwithout a successor. A stale reference is re-researched, never trusted and never silently extended. - A bug turns out to be rooted in a facet the reference lacks. The fix closes with a reference entry, not only a narrative in the design doc.
Do not write one for the project's own behaviour, for anything a single link to a stable spec section covers, or as a tutorial. Scope a reference to what the code depends on: a git reference for a module that only pushes and reads history covers refusals, identity, and credentials, not branching strategy.
What a reference looks like
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.
- 1mo ago Changed 787f48962615
- 1mo ago First seen · 158 lines · 99 tokens per session scan A a4df2b336638
researching-references is a skill published in the GitHub repository pvliesdonk/paperless-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 2,456 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to researching-references, differing in 0 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…