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/heyAyushh/staccWrote 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/heyayushh/stacc/commit)<a href="https://agentmods.dev/commands/heyayushh/stacc/commit"><img src="https://agentmods.dev/badge/commands/heyayushh/stacc/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/heyayushh/stacc/commit"><img src="https://agentmods.dev/badge/commands/heyayushh/stacc/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.00381 |
| Opus 5.5 | $0.00000 | $0.00152 |
| Sonnet 5.5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
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 25d 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.
What it actually says
Commit only (current branch)
Overview
This command is a simple template to commit local changes on the current branch.
It does not handle pushing to the remote or enforcing branch strategies (such as disallowing direct commits to main); it only performs commits that follow the commit message rules.
Preconditions
- There are modified files.
- The commit message format is defined by a rule file such as
.cursor/rules/commit-message-format.mdc.
Steps (non-interactive)
- Review the uncommitted diff and decide on an appropriate commit message (e.g. using
git difforgit diff --cached). - Stage changes (
git add -A). - Commit (
git commit) using an environment variable or argument for the message.
A) Safe one-liner execution (with message argument)
MSG="<Prefix>: <summary (imperative / concise)>" \
git add -A && \
git commit -m "$MSG"
Example:
MSG="fix: remove unnecessary debug log output" \
git add -A && \
git commit -m "$MSG"
B) Step-by-step execution (readability first)
# 1) Inspect changes
git status
git diff
# 2) Stage changes
git add -A
# 3) Commit (edit the message inline)
git commit -m "<Prefix>: <summary (imperative / concise)>"
Notes
- The commit message format and message generation principles should follow
.cursor/rules/commit-message-format.mdc. - Branch strategy (e.g. disallowing direct commits to main) and pushing to the remote (
git push) are out of scope for this command. Define those in project-specific README / CONTRIBUTING / separate commands as needed.
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.
- 25d ago Changed · -99 lines 0e5dc221b7fc
- 1mo ago 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 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 381 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
open
Open a PDF in the in-app viewer panel.
brief-compliance-check
Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Use when verifying format, required sections, word limits, or deliverables before submission. Not for general prose proofreading; use $proofread.
render-figures
Compile all .tex and .typ figure files in a directory.
docs
Document delivery with export to PPTX, DOCX, PDF formats.
pipeline-minutar-pdf
Pipeline completo de sentença judicial a partir de PDF (conversão, linha-tempo, relatório, análise, fundamentação, merge).
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].