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 jurisupport/jurisupport-plugins --skill records-syncgit clone --depth 1 https://github.com/jurisupport/jurisupport-pluginsWrote 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/jurisupport/jurisupport-plugins/records-sync)<a href="https://agentmods.dev/skills/jurisupport/jurisupport-plugins/records-sync"><img src="https://agentmods.dev/badge/skills/jurisupport/jurisupport-plugins/records-sync.svg" alt="Measured on agentmods" 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.00076 | $0.00623 |
| Opus 5 | $0.00038 | $0.00311 |
| Sonnet 5 | $0.00015 | $0.00125 |
| Haiku 4.5 | $0.00008 | $0.00062 |
Grade A, and why
records-sync scanned grade A 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:8767/health The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 6d ago First seen · 58 lines · 76 tokens per session scan A 3b11a5497336
records-sync is a skill published in the GitHub repository jurisupport/jurisupport-plugins (72 stars, last pushed 8d ago), with no licence file. It adds 76 tokens to every session and 623 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other skills, from other repositories
dsar-fulfillment
Daily GDPR data-subject-access-request runbook. Verifies each incoming request from Gmail, locates the subject's data read-only across every relevant Postgres table, compiles an access-or-deletion report in Google Docs within the {{sladays}}-day SLA, and flags it to {{legalreviewchannel}} for a lawyer to approve.…
state-assets-register
Download nightly XML extracts and the XSD for Estonia's State Real Estate Register (RKVR).
Data Retention Schedule Review
Use when reviewing a draft or existing data retention schedule to inventory data categories against stated purposes, collect retention-period facts, flag legal-hold interactions, and surface orphaned-data and vendor-coverage gaps for attorney review.
lgpd-consent-schema
Design the database schema for a versioned, append-only consent ledger that satisfies LGPD Art. 8 (free, informed, unambiguous consent for a specific purpose) and Art. 9 (information rights). Use when user asks for "consent schema", "consent ledger", "schema de consentimento", "Prisma consentimento", "consent…
opensearch-agent-right-to-be-forgotten
Fulfil GDPR "right to be forgotten" / erasure and CCPA deletion requests against OpenSearch by finding and removing a person's personal data — including INDIRECT contextual identification, where an individual is identifiable without their name, email, or ID ever appearing (e.g. "the solo frontend engineer on duty…
db-temporal-history
Audit temporal and lifecycle modeling — soft-delete consistency and its uniqueness/query traps, presence and integrity of an audit/history trail, and retention / GDPR right-to-erasure handling (hard delete vs anonymization, retention windows). Module M8. Feeds the Design & Integrity score (Temporal category).