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.
/plugin marketplace add githits-com/githits-clinpx agentmods add plugins/githits-com/githits-cli/githits-cligit clone --depth 1 https://github.com/githits-com/githits-cliGrade A, and why
githits-cli 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.
This is a copy
91% identical to githits-plugins — 62 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
{
"name": "githits",
"version": "0.11.2",
"description": "The code context layer for AI coding agents",
"author": {
"name": "GitHits"
},
"homepage": "https://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"
]
}
What ships with it
1 file beside plugin.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 First seen · 27 lines scan A efa4e939d7e6
githits-cli is a plugin published in the GitHub repository githits-com/githits-cli (87 stars, last pushed 3d ago), 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. It is 91% identical to githits-plugins, differing in 62 lines, and is treated as a copy.
Other plugins, from other repositories
ultracontext
Cross-agent session portability. Powered by UltraContext.
cross-code-organizer
Organize all your Claude Code memories, skills, MCP servers, and hooks — see what loads globally vs per-project, then move items between scopes.
navigator
Plugin marketplace listing 1 plugin: navigator.
navigator
Finish What You Start - Sessions that last, AI that learns, Features that ship. Context engineering + Theory of Mind + Knowledge Graph + Loop Mode + Task Mode. Features Project Knowledge Graph (unified search, experiential memory), unified workflow orchestration, auto-update on session start, ToM-based verification…
promptly-prompt
Clarity gate: intercepts unclear prompts, forces restate-to-align, then diagnose root cause and reuse the domain's mature practices.
promptly-prompt
Clarity gate for prompts: intercepts unclear requests and forces AI to restate intent to align with the user, then diagnose the root cause and reuse the domain's mature, established practices before proceeding.