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/areal-project/areal/commit-conventionsnpx skills add areal-project/AReaL --skill commit-conventionsgit clone --depth 1 https://github.com/areal-project/AReaLWhat 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.00031 | $0.01256 |
| Opus 5 | $0.00015 | $0.00628 |
| Sonnet 5 | $0.00006 | $0.00251 |
| Haiku 4.5 | $0.00003 | $0.00126 |
Grade A, and why
commit-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 2d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Conventions
Commit message conventions and scope inference rules for the AReaL repository.
When to Use
ALWAYS load this skill when making any git commit in AReaL. This includes:
- Direct commits (
git commit) - Commits during PR creation (
$create-pr//create-pr) - Commits delegated to sub-agents with this skill loaded
- Any agent workflow that produces a commit
Commit Message Format
<type>(<scope>): <subject>
<body>
[Optional sections:]
Key changes:
- change 1
- change 2
Refs: #123, #456
Type Selection
| Type | When to Use |
|---|---|
feat |
New feature or capability |
fix |
Bug fix |
docs |
Documentation only |
gov |
Governance or maintainer changes |
style |
Formatting/style-only changes |
refactor |
Code change without feature/fix |
perf |
Performance improvement |
test |
Adding or fixing tests |
build |
Build system or dependencies |
ci |
CI pipeline or workflow changes |
chore |
Build, deps, config changes |
revert |
Revert a previous commit |
Scope Inference
Infer scope from the primary changed file paths:
| File Path Pattern | Scope |
|---|---|
areal/workflow/ |
workflow |
areal/engine/ |
engine |
areal/reward/ |
reward |
areal/dataset/ |
dataset |
areal/api/ |
api |
areal/utils/ |
utils |
areal/infra/ |
infra |
areal/trainer/ |
trainer |
areal/models/ |
models |
areal/experimental/ |
experimental |
docs/ |
docs |
examples/ |
examples |
AGENTS.md, .agents/, .claude/, .codex/, .opencode/ |
agents |
| Multiple areas | Omit scope or use broader term |
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.
- 2d ago First seen · 181 lines · 31 tokens per session scan A d5d764038726
commit-conventions is a skill published in the GitHub repository areal-project/AReaL (5,708 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 1,256 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
add-cuda-kernel
Rules and steps for creating a compute kernel in RL.cu project.
release
Prepare and publish stable Agent Lightning releases through the repository's version bump, pull-request checks, merge, tag, PyPI trusted-publishing, and versioned-documentation workflows. Use when asked to plan, cut, verify, or explain a release; treat nightly TestPyPI builds as a separate path.
agent-lightning
Provides the action space, tradeoffs, and evaluation context for improving an editable AI agent against a benchmark while preserving its deployment contract. Use when optimizing agent accuracy, cost, latency, or reliability.
bump-go-version
Bumps the Go version to the latest release across go.mod, tools.mod, and Dockerfiles.
nemotron-retrieval-recipes
Use when planning, debugging, tuning, evaluating, exporting, or deploying public Nemotron embed/rerank retrieval recipes.
nemotron-nano3
Reference desk for Nemotron 3 Nano / Llama-Nemotron Nano 3 — architecture, training data, recipes, evaluation, quantization, deployment. Use when the user asks facts about the model rather than building a pipeline.