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 agentmods add skills/jartan-llc/grimoire/github-conventionsnpx skills add Jartan-LLC/grimoire --skill github-conventionsgit clone --depth 1 https://github.com/Jartan-LLC/grimoireWhat 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 | $0.00028 | $0.00507 |
| Opus 5 | $0.00014 | $0.00253 |
| Sonnet 5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
github-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 3d 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.
What it actually says
GitHub Conventions
CRITICAL: #<number> auto-links to issues/PRs on GitHub. Use 1./2./3. for numbered lists and "Finding 1:"/"Item 1:" for labeled items -- never #1, #2, #3 as markers.
Authentication
Never reconfigure auth transport to unblock a command. Don't switch the remote between SSH and HTTPS, add a credential helper, or push to an explicit URL. A missing key or token scope is a missing credential, not a transport problem -- only the user can supply it, and working around it changes config they never asked you to touch, often globally. Stop and ask.
Branches
Feature branches: feature/<description> or feature/issue-<number>
Always check if a branch already exists for an issue before creating a new one.
For sub-issues of a larger feature, branch from the parent feature branch rather than main. Sub-issue work merges back into the parent feature branch, which eventually merges to main.
Commits
Conventional commits format: <type>: description
Types: feat:, fix:, docs:, style:, refactor:, test:, chore:
Optional scope: feat(frontend): description
Issues
Templates in .github/ISSUE_TEMPLATE/ -- read them for section structure.
- Bug reports: must have label
bug - Feature requests: must have label
enhancement
Pull Requests
PR template at .github/PULL_REQUEST_TEMPLATE.md -- read it for section structure.
Use Closes #<number> to link PRs to issues.
Code Reviews
Reviews are posted as PR comments. See review-format.md for the
recommended structure -- severity buckets and the #N footgun to avoid in the summary.
Implementation Plans
Plans are posted as issue comments and saved to .claude/workspace/. See plan-format.md for the recommended structure.
What ships with it
2 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.
- 3d ago First seen · 54 lines · 28 tokens per session scan A d0d48312f8e3
github-conventions is a skill published in the GitHub repository Jartan-LLC/grimoire (2 stars, last pushed 15d ago), licensed MIT. It adds 28 tokens to every session and 507 once invoked, about $0.0001 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-31.
Other skills, from other repositories
git-commit-message
Auto-generates conventional commit messages from git diffs with tiered format enforcement. Analyzes staged changes to produce meaningful commit messages following Conventional Commits specification.
git-hygiene
Execute explicitly requested version-control mutations safely, including staging, commits, branches, merges, rebases, conflict resolution, undo operations, and pull-request preparation. Always use before force push, reset, clean, history rewrite, or deletion. Do not trigger for read-only status, diff, log, blame, or…
conventional-commits
Create Git commits using Conventional Commits with a scoped Chinese subject and a concise bullet-list body. Use when Codex is asked to commit changes, prepare a commit message, amend a commit message, or review whether a proposed commit follows the required format.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…