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 haocn-ops/git-topnpx agentmods add plugins/haocn-ops/git-top/marketplacegit clone --depth 1 https://github.com/haocn-ops/git-topGrade A, and why
git-top-tools 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:
- git-top — 88% identical, 33 lines differ
What it actually says
{
"name": "git-top-tools",
"owner": {
"name": "Git.Top",
"url": "https://github.com/haocn-ops/git-top"
},
"description": "Git.Top project selection tools for Claude Code.",
"plugins": [
{
"name": "git-top",
"source": "./plugins/git-top",
"description": "Evidence-backed open-source project decisions through Git.Top REST and MCP.",
"version": "0.1.0",
"author": {
"name": "Git.Top",
"url": "https://github.com/haocn-ops/git-top"
},
"homepage": "https://git.top/connect?source=claude-code-marketplace",
"repository": "https://github.com/haocn-ops/git-top",
"license": "MIT",
"category": "Developer tools",
"tags": ["open-source", "project-selection", "mcp", "agents"]
}
]
}
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 · 26 lines scan A 6f41e0492099
git-top-tools is a plugin published in the GitHub repository haocn-ops/git-top (0 stars, last pushed yesterday), licensed MIT. 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-31.
Other plugins, from other repositories
memtrace-skills
Memtrace skills for codebase exploration, code search, relationship analysis, temporal evolution, blast radius impact, code quality, graph algorithms, API topology, GitHub PR code review, multi-agent fleet coordination (branch-scoped intents, conflict classification, and agent-judged Class C resolution), and…
pkup-gen
Plugin marketplace listing 1 plugin: pkup-tools.
lockedin
Personal experience knowledge graph for Claude Code.
stellavault
Stellavault — local-first second brain plugins for Claude Code.
cfahed
Plugin marketplace listing 1 plugin: bmad-github.
the-open-agent
Plugin marketplace listing 1 plugin: oss-skills.