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/githits-com/githits-cliWrote 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/plugins/githits-com/githits-cli/marketplace)<a href="https://agentmods.dev/plugins/githits-com/githits-cli/marketplace"><img src="https://agentmods.dev/badge/plugins/githits-com/githits-cli/marketplace/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/plugins/githits-com/githits-cli/marketplace"><img src="https://agentmods.dev/badge/plugins/githits-com/githits-cli/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
githits-plugins marketplace 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- githits — 91% identical, 67 lines differ
What it actually says
{
"name": "githits-plugins",
"owner": {
"name": "GitHits",
"email": "[email protected]"
},
"metadata": {
"description": "The code context layer for AI coding agents",
"version": "0.30.0"
},
"plugins": [
{
"name": "githits",
"version": "0.30.0",
"description": "The code context layer for AI coding agents",
"author": {
"name": "GitHits"
},
"homepage": "https://docs.githits.com",
"repository": "https://github.com/githits-com/githits-cli",
"license": "Apache-2.0",
"keywords": [
"githits",
"context layer",
"public open-source",
"open-source code",
"code search",
"package documentation",
"documentation search",
"package metadata",
"vulnerabilities",
"changelogs",
"dependency graphs",
"upgrade evidence",
"implementation examples"
],
"source": {
"source": "url",
"url": "https://github.com/githits-com/githits-cli.git"
},
"category": "developer-tools"
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed 3622115907b5
- 4d ago Changed 13515ec08546
- 7d ago Changed a85df60eb110
- 9d ago Changed 1813e601c0bd
- 10d ago Changed 504206bf09bf
- 11d ago Changed 44369c95a378
- 15d ago Changed 5197aa6498bc
- 16d ago Changed 2e9965a31ca2
- 18d ago Changed 6f9b611d71cb
- 21d ago First seen · 45 lines scan A fd06d65bcd77
githits-plugins marketplace is a plugin published in the GitHub repository githits-com/githits-cli (115 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
bounty-board
Turns your repo's tech debt into an aging bounty economy. A SessionStart hook scans tracked files and prices each TODO/FIXME/HACK/skip as a wanted-poster bounty whose XP grows with its git-blame age, injects the top 3 as opportunistic side quests, and, via a PostToolUse hook, verifies and pays out bounties that…
pr-provenance-stamp
Embeds a reviewer-facing provenance receipt into your PR body when Claude runs gh pr create (or glab mr create). A PostToolUse hook (async, zero added latency) records a per-session ledger: tool calls, agent-authored lines, and every test/typecheck command with its real exit code; a PreToolUse (Bash) hook then rewr.
standup-autopilot
Turns what your agents ACTUALLY did into a standup: captured from session transcripts (not commits/tickets, which miss uncommitted work, real test exit codes, and unresolved errors) and rolled up cross-repo. Stop/SessionEnd snapshot each session's outcome (task, branch + diffstat, tests + exit codes, PRs, blockers) to.
stash
Connect Claude Code to Stash — stream activity to your Stash and collaborate with your other agents.
ultracontext
Cross-agent session portability. Powered by UltraContext.
faf
Persistent Project Context for AI — IANA-registered .faf format. Run /faf to score your project in Claude Code; install the CLI via bunx faf or npm install -g faf-cli for the full toolkit.