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/rashadansari/myagents/commitgit clone --depth 1 https://github.com/RashadAnsari/myagentsWhat 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.00004 | $0.00235 |
| Opus 5 | $0.00002 | $0.00118 |
| Sonnet 5 | $0.00001 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00023 |
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 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.
This is a copy
89% identical to commit — 6 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.
What it actually says
Context
The ! prefix on each line below runs the shell command inline and injects its output before the prompt is submitted.
- Current git status: !
git status - Current git diff (staged and unstaged changes): !
git diff HEAD - Current branch: !
git branch --show-current - Recent commits: !
git log --oneline -10
Your task
Based on the above changes, create a single git commit.
Infer the commit message format from the recent commits shown above: match the exact style, prefix convention, casing, and structure used in this project. Do not impose an external convention if the project already has one.
You have the capability to call multiple tools in a single response. Stage and create the commit using a single message. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.
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 · 22 lines · 4 tokens per session scan A cf11f97c0e46
commit is a command published in the GitHub repository RashadAnsari/myagents (6 stars, last pushed 25d ago), licensed MIT. It adds 4 tokens to every session and 235 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to commit, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
memory-review
Display current memory state with timestamps, sizes, and staleness indicators.
git
Unified git operations - commits, pull requests, and issue management.
setup:javascript
Set up a new JavaScript/Node.js project with modern tooling and Claude framework integration.
fix
Universal debugging and fix application with semantic code analysis.
work
Work unit management: list, continue, checkpoint, switch.
index
Create persistent project understanding via PROJECTMAP.md.