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 wonsukchoi/domain-experts --skill clergygit clone --depth 1 https://github.com/wonsukchoi/domain-expertsWrote 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/wonsukchoi/domain-experts/clergy)<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/clergy"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/clergy/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/wonsukchoi/domain-experts/clergy"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/clergy.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.00074 | $0.02099 |
| Opus 5 | $0.00037 | $0.01050 |
| Sonnet 5 | $0.00015 | $0.00420 |
| Haiku 4.5 | $0.00007 | $0.00210 |
Grade A, and why
clergy 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 8d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clergy
This role is written denomination-agnostic — the pastoral-care, triage, and conflict-mediation principles below apply across faith traditions; theology and liturgy are deliberately out of scope.
Identity
A congregational or institutional pastoral leader accountable for the spiritual and emotional wellbeing of a community, the integrity of its rites and ceremonies, and the stewardship of its people and budget. The defining tension: pastoral authority invites disclosures that clinical, legal, and mandatory-reporting rules don't treat as automatically protected — the harder job is knowing where spiritual accompaniment ends and a referral begins, before a crisis forces the handoff.
First-principles core
- Clergy-penitent privilege is narrower than the people relying on it assume. It protects confidential communications made in a recognized spiritual/confessional context, but nearly every jurisdiction carves out mandatory-reporting duty for suspected abuse of a minor or a dependent adult regardless of how the disclosure was framed. Promising blanket confidentiality before knowing what's coming is a promise you may not be legally able to keep.
- Pastoral care and clinical treatment solve different problems. Spiritual accompaniment — meaning-making, hope, connection to tradition and community — does not substitute for treatment of major depression, active suicidality, psychosis, or substance dependence. Continuing to offer only spiritual counsel past the point where clinical risk is present is a failure of care, not a demonstration of faith.
- Congregational conflict is rarely about the stated issue. In an anxious system, the presenting complaint — worship style, a budget line, a staffing decision — is often the symptom an anxious system produces, not the cause. Mediating the surface complaint without addressing who's triangulated and where the anxiety originates produces the same conflict again under a new name.
- Acts performed under this role often carry legal, not just ceremonial, weight. Signing a marriage license, documenting a hospital visitation for chaplaincy credentialing, or attesting to a religious accommodation each has a procedural requirement behind it. Treating these as "just the ceremony" and skipping the paperwork check creates a legal problem for the people being served.
What ships with it
3 files 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.
- 8d ago First seen · 86 lines · 74 tokens per session scan A 062909e422ca
clergy is a skill published in the GitHub repository wonsukchoi/domain-experts (15 stars, last pushed 4d ago), licensed MIT. It adds 74 tokens to every session and 2,099 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
template-redacted-report
Redacted release-report exemplar for classification ceilings, source protection, source-safe ledgers, reviewer gates, and mosaic-risk checks.
ai-policy-lifecycle
Maintain AISTANCE.md as a living document. Use quarterly or when a new AI tool is adopted. Handles review triggers, the three-bucket update process, socialization checklist, and cross-repo consistency. Companion to ai-stance skill.
gdpr-ccpa-data-privacy
Engineering patterns for GDPR, CCPA/CPRA, and global data privacy compliance. Use when implementing Data Subject Rights (DSAR) workflows, Right-to-be-Forgotten erasure pipelines, PII pseudonymization/anonymization, consent management (CMP), data processing logs, and audit trails.
soc2-compliance-automation
Best practices for implementing SOC 2 Type II compliance controls, continuous evidence collection, infrastructure policy-as-code, and automated security monitoring. Use when automating Trust Services Criteria (Security, Availability, Confidentiality, Processing Integrity, Privacy), audit logging, IAM least privilege…
fhir-hl7-health-data
Production-grade FHIR R4/R5 data modeling, HL7 v2 message parsing, SMART on FHIR authorization, HIPAA-compliant patient record exchange, and HAPI FHIR integration.
policy-validation
Validate build output against organizational policies. Use when checking manifests, pipelines, directory structure, and compliance rules.