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/nomadamas/autorag-research/commit-pushgit clone --depth 1 https://github.com/NomaDamas/AutoRAG-ResearchWhat 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.00013 | $0.00292 |
| Opus 5 | $0.00006 | $0.00146 |
| Sonnet 5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
commit-push 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.
What it actually says
Perform a checkpoint commit and push to the current branch:
- Run
git statusto review both modified and untracked files - For untracked files: Check file contents to ensure they don't contain private info (API keys, tokens, passwords, credentials). Skip files like
.env,*credentials*,*secret*,*token*files. - Stage all appropriate files including new files with
git add(exclude sensitive files) - Run
git diff --stagedto review what will be committed - Create a clear, descriptive commit message based on the actual changes
- Push to the current remote branch
Files to NEVER add:
.env,.env.*- Files containing API keys, tokens, passwords, or credentials
*secret*,*credential*,*token*files
Commit message format:
- Use imperative mood (e.g., "Add feature" not "Added feature")
- First line should be concise summary (max 72 chars)
- Add body if changes are complex
This is a checkpoint commit for tracking progress.
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.
- 2d ago First seen · 26 lines · 13 tokens per session scan A 998bfcdb5e02
commit-push is a command published in the GitHub repository NomaDamas/AutoRAG-Research (148 stars, last pushed 24d ago), licensed Apache-2.0. It adds 13 tokens to every session and 292 once invoked, about $0.0001 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.
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.