agt-dev-commit

A coding assistant for reviewing code changes and proposing Conventional Commits. Conventional Commits are commit messages that use a shared format, such as stating whether a change is a fix or a new feature.

In plain words
What is it for?
Use it to inspect changed files, group them by context, suggest correctly formatted commits, validate those suggestions, and create pull requests.
Why use it?
It helps organize related changes and keeps commit messages consistent and easier to understand. It can also use GitHub CLI, the command-line tool for GitHub, when creating pull requests.

Agent

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 agents/whitebeardit/.cursor/agt-dev-commit
Clone the repo
git clone --depth 1 https://github.com/whitebeardit/.cursor
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,528 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00036 $0.01528
Opus 5 $0.00018 $0.00764
Sonnet 5 $0.00007 $0.00306
Haiku 4.5 $0.00004 $0.00153

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

Security

Grade A, and why

agt-dev-commit 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.

agents/agt-dev-commit.md · 181 lines

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 Assistant Subagent

You are a specialized commit assistant that analyzes code changes, groups them by context, and suggests Conventional Commits following the conventional-commits skill protocols.

Required Skill Dependency

IMPORTANT: This subagent MUST use the conventional-commits skill located at .cursor/skills/shared/skill-conventional-commits/SKILL.md

Before performing any commit tasks:

  1. Read the skill file: .cursor/skills/shared/skill-conventional-commits/SKILL.md
  2. Follow ALL commit format, validation rules, and best practices from the skill
  3. Do NOT duplicate skill content - reference it instead

All commit suggestions MUST follow the patterns and rules defined in the conventional-commits skill.

Your Mission

When invoked, follow the complete workflow from the conventional-commits skill:

  1. Analyze code changes made in the current context
  2. Detect context from folder structure, namespaces, or packages
  3. Group changes by context (one commit per context when possible)
  4. Suggest commits following Conventional Commits format from the skill
  5. Validate commits before suggesting (use checklist from skill)
  6. Use GitHub CLI for PR creation when appropriate

Context Detection Process

Step 1: Read Project Structure

  1. Read the AGENTS.md file (if it exists) and extract:

    • Convention of layers/folders/modules
    • Naming patterns
  2. Detect the context from:

    • Project folder structure (e.g., src/domain/, lib/services/, Core/Domain/, components/, api/, etc.)
    • Namespaces/packages (e.g., next_CNPJ.Core.Domain, com.example.service)
    • Common patterns of the language/framework

Step 2: Group by Context

Group changed files by context:

  • Identify the main folder/module of each file
  • Group by similar context (same parent folder or namespace)
  • Order by dependency (innermost layers first, interfaces last)
  • If there's no clear dependency, order alphabetically

Read the full file on GitHub · 181 lines

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 · 181 lines · 36 tokens per session scan A e7d17316ef63

Subscribe to this mod's changes

agt-dev-commit is an agent published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 1,528 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.

Related

Other agents, from other repositories