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 commands/heyayushh/stacc/commitgit clone --depth 1 https://github.com/heyAyushh/staccWhat 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.00000 | $0.00980 |
| Opus 5 | $0.00000 | $0.00490 |
| Sonnet 5 | $0.00000 | $0.00196 |
| Haiku 4.5 | $0.00000 | $0.00098 |
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 yesterday.
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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Changes
Commit local changes following conventional commit message format. Supports intelligent splitting of large change sets into multiple atomic commits.
Overview
This command stages and commits changes with properly formatted messages. For large or complex change sets, it analyzes changes and creates multiple atomic commits grouped by logical concern.
Preconditions
- Modified or untracked files exist
- Working directory is inside a git repository
Steps
-
Assess the change set
git status git diff --stat -
Determine commit strategy
- Single commit: All changes are related to one concern (< 10 files, single feature/fix)
- Multiple commits: Changes span multiple concerns (different features, unrelated fixes, mixed refactoring)
-
For single commit: Stage all and commit
git add -A git commit -m "<prefix>: <summary>" -
For multiple commits: Group and commit separately (see Multi-Commit Workflow below)
Commit Message Format
Use conventional commit prefixes:
feat: New featurefix: Bug fixrefactor: Code refactoring (no behavior change)perf: Performance improvementtest: Testsdocs: Documentationbuild: Build system or dependenciesci: CI/CD configurationchore: Maintenance tasksstyle: Code style (formatting, semicolons)revert: Revert previous commit
Message Structure
<prefix>: <summary (imperative, ~50 chars)>
[optional body with bullet points]
[optional footer: Refs #issue, BREAKING CHANGE, Co-Authored-By]
Multi-Commit Workflow
When changes span multiple concerns, split into atomic commits:
1. Analyze and group changes
# See all changes
git status
# Group mentally or list by concern:
# - Feature A: src/feature-a.ts, tests/feature-a.test.ts
# - Bug fix: src/utils.ts
# - Docs: README.md, docs/api.md
2. Commit each group separately
# Commit group 1
git add src/feature-a.ts tests/feature-a.test.ts
git commit -m "feat: add feature A with validation"
# Commit group 2
git add src/utils.ts
git commit -m "fix: handle null input in parseData"
# Commit group 3
git add README.md docs/api.md
git commit -m "docs: update API documentation"
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.
- yesterday First seen · 153 lines · 0 tokens per session scan A f6a55fe00783
commit is a command published in the GitHub repository heyAyushh/stacc (3 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 980 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.