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.
git clone --depth 1 https://github.com/whitebeardit/.cursorWrote 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/agents/whitebeardit/.cursor/agt-dev-commit)<a href="https://agentmods.dev/agents/whitebeardit/.cursor/agt-dev-commit"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-dev-commit/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/agents/whitebeardit/.cursor/agt-dev-commit"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-dev-commit.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.00036 | $0.01528 |
| Opus 5.5 | $0.00014 | $0.00611 |
| Sonnet 5.5 | $0.00007 | $0.00306 |
| Haiku 4.5 | $0.00004 | $0.00153 |
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 1mo 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 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:
- Read the skill file:
.cursor/skills/shared/skill-conventional-commits/SKILL.md - Follow ALL commit format, validation rules, and best practices from the skill
- 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:
- Analyze code changes made in the current context
- Detect context from folder structure, namespaces, or packages
- Group changes by context (one commit per context when possible)
- Suggest commits following Conventional Commits format from the skill
- Validate commits before suggesting (use checklist from skill)
- Use GitHub CLI for PR creation when appropriate
Context Detection Process
Step 1: Read Project Structure
-
Read the
AGENTS.mdfile (if it exists) and extract:- Convention of layers/folders/modules
- Naming patterns
-
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
- Project folder structure (e.g.,
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
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.
- 1mo ago First seen · 181 lines · 36 tokens per session scan A e7d17316ef63
agt-dev-commit is an agent published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 7mo ago), licensed MIT. It adds 36 tokens to every session and 1,528 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
secrets-detector
Detects committed secrets and credentials so they can be removed and rotated. Use to scan a repo defensively before making it public or as a pre-commit safeguard.
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
commit
Runs the auto-commit skill.
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.