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/ankitaa186/host-terminal-mcp/gitgit clone --depth 1 https://github.com/ankitaa186/host-terminal-mcpWrote 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/ankitaa186/host-terminal-mcp/git)<a href="https://agentmods.dev/commands/ankitaa186/host-terminal-mcp/git"><img src="https://agentmods.dev/badge/commands/ankitaa186/host-terminal-mcp/git.svg" alt="Measured on agentmods" 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.00014 | $0.00528 |
| Opus 5 | $0.00007 | $0.00264 |
| Sonnet 5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
git 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 5d 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
Git Repository Operations
Interact with git repositories using read-only git commands.
Workflow
- Verify we're in a git repository
- Parse the git subcommand from user input
- Execute the git command via
~~terminal - Format and present the results
Allowed Git Commands
The following git operations are pre-approved by default:
| Command | Description |
|---|---|
git status |
Working tree status |
git log |
Commit history |
git diff |
Show changes |
git show |
Show commit details |
git branch |
List branches |
git remote |
List remotes |
git tag |
List tags |
git stash list |
List stashes |
git blame |
Line-by-line authorship |
git shortlog |
Summarize commits |
git describe |
Describe commit |
git config --get |
Read config values |
git config --list |
List all config |
git rev-parse |
Parse revisions |
Usage Examples
Check status
/git status
View recent commits
/git log --oneline -10
See what changed
/git diff
/git diff HEAD~1
/git diff --staged
List branches
/git branch -a
Show commit details
/git show HEAD
/git show abc1234
Find who changed a line
/git blame src/main.py
Write Operations
Git write operations (commit, push, pull, merge, rebase, etc.) are not in the default allowlist. To enable them:
- Switch to
askmode and approve individually - Or add them to your
config.yamlallowlist
Tips
- Use
--onelinewithgit logfor concise output - Use
-n <number>to limit results - Combine with grep:
/shell git log --oneline | grep "fix"
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.
- 5d ago First seen · 91 lines · 14 tokens per session scan A 06dcd4faa6dd
git is a command published in the GitHub repository ankitaa186/host-terminal-mcp (0 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 528 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-09-01.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.