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/elanmed/agent-jsWrote 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/elanmed/agent-js/commit)<a href="https://agentmods.dev/commands/elanmed/agent-js/commit"><img src="https://agentmods.dev/badge/commands/elanmed/agent-js/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/elanmed/agent-js/commit"><img src="https://agentmods.dev/badge/commands/elanmed/agent-js/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.00292 |
| Opus 5.5 | $0.00000 | $0.00117 |
| Sonnet 5.5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
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 2mo 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
Run git log --oneline -20 to see previous commit messages and understand the style.
Run git diff --staged --name-only to check if there are any staged files.
If no files are staged, run git add -A to stage all changes.
Run git diff --staged to see the changes.
Look at the changes and decide:
- If changes are related and belong together, create a single commit
- If changes affect different areas (e.g., tests vs source, docs vs code, unrelated features), create separate commits
When splitting into multiple commits:
- Stage files for the first logical group with
git add <files> - Commit with an appropriate message
- Repeat for each group
Write commit messages that:
- Use conventional commit format:
<type>: <description> - Common types:
add:,fix:,refactor:,docs:,tests:,misc: - Use lowercase only
- Use commas to separate multiple changes in one commit
- Fit on a single line
- Are descriptive but concise
Before committing, present the proposed commit message(s) to the user and ask for confirmation.
If the user confirms the message is good, run git commit -m "<message>" for each commit.
If the user says the message is not good, ask them to provide a new commit message and use exactly what they provide.
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.
- 2mo ago First seen · 34 lines · 0 tokens per session scan A 2b775661edd9
commit is a command published in the GitHub repository elanmed/agent-js (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 292 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
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.
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.
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.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.