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/NaverPayDev/naverpay-pluginsWrote 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/naverpaydev/naverpay-plugins/git-commands)<a href="https://agentmods.dev/plugins/naverpaydev/naverpay-plugins/git-commands"><img src="https://agentmods.dev/badge/plugins/naverpaydev/naverpay-plugins/git-commands/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/naverpaydev/naverpay-plugins/git-commands"><img src="https://agentmods.dev/badge/plugins/naverpaydev/naverpay-plugins/git-commands.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
naverpay-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 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
{
"name": "naverpay-git",
"description": "Streamlines git workflow with atomic commits and draft pull requests",
"author": {
"name": "NaverPayDev"
},
"repository": "https://github.com/NaverPayDev/naverpay-plugins",
"keywords": ["naverpay", "claude-plugin", "claude", "plugin", "commit", "pr"]
}
What it installs
The manifest is a name and a version. 2 commands travel with it, and installing the plugin installs all of them — 27 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 10 lines scan A c812f0d4ce2e
naverpay-git is a plugin published in the GitHub repository NaverPayDev/naverpay-plugins (2 stars, last pushed 5mo ago), 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.
naverpay-git compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| naverpay-gitNaverPayDev/naverpay-plugins | Plugin | 2 | 5mo ago | MIT | A | — | Claude Code |
| git-sidebardavila7/claude-code-templates | Plugin | 33k | today | MIT | A | — | Claude Code |
| git-prCasper-Studios/casper-marketplace | Plugin | 15 | 8d ago | MPL-2.0 | A | — | Claude Code |
| gittechnicalpickles/pickled-claude-plugins | Plugin | 12 | yesterday | MIT | A | — | Claude Code |
| casKasempiternal/Claude-Agent-System | Plugin | 16 | 3mo ago | MIT | A | — | Claude Code |
| code-qualitydanielbodnar/skills | Plugin | 2 | 3mo ago | MIT | A | — | Claude Code |
| prekneoeinstein/claude-plugins | Plugin | 4 | 5d ago | none | A | — | Claude Code |