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/yezannnnn/agentGroupWrote 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/commands/yezannnnn/agentgroup/commit)<a href="https://agentmods.dev/commands/yezannnnn/agentgroup/commit"><img src="https://agentmods.dev/badge/commands/yezannnnn/agentgroup/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/commands/yezannnnn/agentgroup/commit"><img src="https://agentmods.dev/badge/commands/yezannnnn/agentgroup/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.00000 | $0.01484 |
| Opus 5.5 | $0.00000 | $0.00594 |
| Sonnet 5.5 | $0.00000 | $0.00297 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
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.
This is a copy
100% identical to commit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze changes and create logical git commits with user confirmation
Follow these instructions from top to bottom.
Create a TODO with EXACTLY these 6 items
- Parse arguments and analyze git status
- Review changes and group by logical commits
- Propose commit structure and messages
- Check if user approval is necessary
- Execute approved commits
- Report commit results
1 · Analyze git status and parse arguments
- Run these commands in parallel for maximum efficiency:
git status,git diff --staged,git diff - List all changed files with their folder structure to understand the scope
CRITICAL: Argument Interpretation Rules
Context Provided (when <$ARGUMENTS> contains text):
- If YOLO is part of the <$ARGUMENTS> it is meant to skip user Approval (see Step 4 on your Todo)
- The other text in <$ARGUMENTS> represents a task ID, sprint ID, or other contextual identifier provided by the user
- This is NOT a file path - it's a semantic context for filtering changes
- PRIMARY FOCUS: Only commit files directly related to this context
- SECONDARY CONSIDERATION: After handling the primary context, ask if user wants to commit other unrelated changes
Task ID Pattern (e.g., T01_S02, TX03_S01, T003):
- Sprint Tasks:
T<NN>_S<NN>format (e.g., T01_S02, T03_S02) - Completed Sprint Tasks:
TX<NN>_S<NN>format (e.g., TX01_S02, TX03_S01) - General Tasks:
T<NNN>format (e.g., T001, T002) - Completed General Tasks:
TX<NNN>format (e.g., TX001, TX002) - Search for this task ID in:
.simone/03_SPRINTS/directory (for sprint tasks).simone/04_GENERAL_TASKS/directory (for general tasks)- Task metadata in files (look for
task_id: T01_S02in frontmatter) - Git diff content (to see if code comments or commits reference the task)
- Identify ALL files that were modified as part of this task's implementation
- This includes: source code, tests, configuration, and the task documentation file itself
Sprint ID Pattern (e.g., S01, S02):
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 · 142 lines · 0 tokens per session scan A 79a791b08da0
commit is a command published in the GitHub repository yezannnnn/agentGroup (150 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,484 tokens. A static security scan graded it A with 0 findings. It is 100% identical to commit, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.