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 psenger/catholic-ai-skills --skill conventionsgit clone --depth 1 https://github.com/psenger/catholic-ai-skillsWrote 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/psenger/catholic-ai-skills/conventions)<a href="https://agentmods.dev/skills/psenger/catholic-ai-skills/conventions"><img src="https://agentmods.dev/badge/skills/psenger/catholic-ai-skills/conventions/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/psenger/catholic-ai-skills/conventions"><img src="https://agentmods.dev/badge/skills/psenger/catholic-ai-skills/conventions.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.00115 | $0.00885 |
| Opus 5 | $0.00057 | $0.00443 |
| Sonnet 5 | $0.00023 | $0.00177 |
| Haiku 4.5 | $0.00012 | $0.00089 |
Grade A, and why
conventions 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 11d 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
100% identical to conventions — 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventions — ai-agent-skills
Commit Messages
Format: type(scope): subject
- Subject: imperative mood, lowercase, no trailing period, ≤72 characters
- Scope: the skill name (
vault-scribe,handoff) or a repo area (release,ci,readme) - Body: optional — explain why, not what; wrap at 72 chars
- Footer:
Closes #NorFixes #Nfor GitHub issues;BREAKING CHANGE: <desc>for breaking changes
Types
| Type | When |
|---|---|
feat |
New skill or new capability in an existing skill |
fix |
Bug fix in a skill's behaviour or instructions |
chore |
Release commits, tooling, config — no production change |
docs |
README, CHANGELOG, CONTRIBUTING only |
refactor |
Skill restructure with no behaviour change |
test |
Eval additions or changes |
Release commit — always exactly:
chore(release): cut vX.Y.Z release
Examples
feat(handoff): add RESUME workflow and proactive suggestion trigger
fix(vault-scribe): prevent incompatible TOC directives
Closes #1
Branch Names
Pattern: type/issue-number-short-description
feature/14-add-handoff-skill
fix/23-vault-scribe-toc
chore/release-v1-1-0
feature/for new skills or new capabilitiesfix/for bug fixeschore/for release and tooling work- Always include the issue number when one exists
- 2–4 words, hyphenated, no version dots (use dashes)
Pull Requests
Title: same format as a commit — type(scope): subject
Body:
## Summary
- <bullet 1>
- <bullet 2>
## Issue
Closes #N
## Test plan
- [ ] Skill activates on expected triggers
- [ ] Output matches documented format
- [ ] No regressions in adjacent skills
- 2–4 summary bullets
- Always link the issue
- Test plan as checkboxes
CHANGELOG Entries (Keep a Changelog 1.1.0)
What ships with it
4 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.
- 11d ago First seen · 131 lines · 115 tokens per session scan A 3eb423bc8db1
conventions is a skill published in the GitHub repository psenger/catholic-ai-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 115 tokens to every session and 885 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to conventions, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.