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 zgbrenner/agentcounsel --skill custody-parenting-facts-chronologygit clone --depth 1 https://github.com/zgbrenner/agentcounselWrote 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/zgbrenner/agentcounsel/custody-parenting-facts-chronology)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/custody-parenting-facts-chronology"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/custody-parenting-facts-chronology/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/zgbrenner/agentcounsel/custody-parenting-facts-chronology"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/custody-parenting-facts-chronology.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.00033 | $0.01648 |
| Opus 5 | $0.00016 | $0.00824 |
| Sonnet 5 | $0.00007 | $0.00330 |
| Haiku 4.5 | $0.00003 | $0.00165 |
Grade A, and why
Custody / Parenting Facts Chronology 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Custody / Parenting Facts Chronology
Purpose
Build a source-cited chronology of parenting and caregiving facts — caregiving roles, exchanges, school and medical involvement, communications, incidents, missed visits, relocation facts, and child-related records — so a qualified, licensed attorney has an organized factual timeline for a custody or parenting dispute. This skill organizes dated events from the provided documents; it recommends no custody outcome and no parenting time.
Use When
- A custody or parenting dispute needs an organized, sourced timeline of caregiving and parenting facts.
- Communications, records, and incident notes must be ordered by date before substantive review.
- An attorney needs a chronology of exchanges, missed visits, school/medical involvement, or relocation facts.
Required Inputs
- The document set — communications and messages, school and medical records, incident notes, police reports if provided, calendars and parenting schedules, and existing orders — with source references.
- The parties, their roles, and the children involved (ages and roles as stated, with identifiers masked) — or
not provided. - Any existing custody, parenting, or protective orders — or
not provided. - The jurisdiction and the case stage — or
not provided, jurisdiction flagged[verify jurisdiction]. - For each event, whether the user states it is disputed or undisputed — otherwise
not provided. - Any dates the user supplies, echoed verbatim and marked
[deadline verification required].
If the document set, the parties, or the children involved is missing, record it as not provided and return the missing-information list first. Build the chronology only from provided documents.
Do Not Use When
- The request is for a custody recommendation, a parenting-time allocation, or a fitness assessment.
- The request is for legal advice or a litigation strategy as a final answer.
- The goal is to organize a parenting schedule's logistics (use
parenting-schedule-facts-organizer). - The goal is to review a custody order's clarity (use
custody-order-review-checklist).
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.
- 12d ago First seen · 109 lines · 33 tokens per session scan A 06af9284c889
Custody / Parenting Facts Chronology is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 1,648 once invoked, about $0.0002 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
legal-research
A legal research skill for finding and analysing laws and court cases, including similar cases. It requires access to a reliable legal research database before producing a formal report.
document-fill
A document-filling assistant that uses a supplied template and case files to fill in forms, contracts, or legal documents. It also reports where each filled value came from and which details are missing.
contract-review
A contract-review workflow for agreements governed by Chinese law, United States law, or both. It examines clauses one by one and produces a list of legal-risk questions, with an optional marked-up Word document.
fedramp
Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026). Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document…
eu-cra
Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 — mandatory cybersecurity and vulnerability handling requirements for all products with digital elements (PDEs) sold in the EU. Use this skill for gap analysis, product classification (Default / Class I / Class II), conformity assessment route…
aenderungsvorbehalt-308
Für Änderungsvorbehalt 308: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.