commit-guidelines

A guide for preparing Git commits or Jujutsu changesets when a repository has uncommitted work or its history needs editing. It covers commits, amendments, splitting changes, changesets, and pull-request history.

In plain words
What is it for?
Use it when inspecting a dirty worktree, creating or amending commits, splitting changes, preparing changesets, or changing commit history.
Why use it?
It helps preserve unrelated work and keep changes grouped into clear, reviewable units. It also provides a process for safely handling existing repository changes before committing or rewriting history.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/firma-ai/openfirma/commit-guidelines
Any agent
npx skills add Firma-AI/openfirma --skill commit-guidelines
Clone the repo
git clone --depth 1 https://github.com/Firma-AI/openfirma

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 934 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00934
Opus 5 $0.00000 $0.00467
Sonnet 5 $0.00000 $0.00187
Haiku 4.5 $0.00000 $0.00093

Measured 2d ago against content hash 5c8b6bb39a28, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

commit-guidelines 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.

.skills/commit-guidelines/SKILL.md · 135 lines

The source is not reproduced here

Licensed GPL-3.0

The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. 2d ago First seen · 135 lines · 0 tokens per session scan A 5c8b6bb39a28

Subscribe to this mod's changes

commit-guidelines is a skill published in the GitHub repository Firma-AI/openfirma (114 stars, last pushed 4d ago), licensed GPL-3.0. It costs nothing until one of its globs matches a file; then it loads 934 tokens. 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.

Related

Other skills, from other repositories

orloj-generator

Interactive scaffold generator for Orloj multi-agent systems. Use this skill whenever someone wants to create, set up, scaffold, bootstrap, or generate an Orloj agent system, pipeline, swarm, or hierarchy. Also trigger when users mention "orlojctl init", ask how to get started with Orloj, want to build a multi-agent…

OrlojHQ/orloj · 168 tokens

nio-action

Nio runtime action safety evaluator. Use when the user asks whether a specific runtime action is safe — e.g. "is it safe to run ", "should I allow this curl/POST", "evaluate this file write / secret access", "check this action with nio". Returns allow/deny/confirm. Focused single-purpose skill; for other Nio…

core0-io/nio · 83 tokens

nio-scan

Nio code/skill execution-risk scanner. Use when the user wants to scan a file, repo, directory, or skill for execution risks — e.g. "scan this code for risks", "is this file/plugin dangerous", "check this repo for malicious code", "run nio scan on ". Focused single-purpose skill; for other Nio operations use /nio.

core0-io/nio · 81 tokens

nio-doctor

Nio config validator + connectivity check. Use when the user wants to validate their Nio setup — e.g. "run nio doctor", "is my nio config valid / working", "test my OAuth / external endpoint / LLM connectivity", "why isn't my scorer firing". Focused single-purpose skill; for other Nio operations use /nio.

core0-io/nio · 75 tokens

nio-external-score

Nio external scoring-endpoint snapshot. Use when the user asks about their current Nio/risk scores from configured external scoring endpoints — e.g. "what's my Nio score", "tell me the nio score", "check my external/guardrail endpoint scores", "what do my scoring services return right now", "list the current risk…

core0-io/nio · 97 tokens

nio-report

Nio execution audit report. Use when the user wants to review recent agent execution activity — e.g. "show my nio report", "what did nio block recently", "show the audit log / recent activity", "any diagnostics / errors in nio". Read-only. Focused single-purpose skill; for other Nio operations use /nio.

core0-io/nio · 72 tokens