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 Astro-Han/claude-pacenpx agentmods add plugins/astro-han/claude-pace/marketplacegit clone --depth 1 https://github.com/Astro-Han/claude-paceWrote 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/astro-han/claude-pace/marketplace)<a href="https://agentmods.dev/plugins/astro-han/claude-pace/marketplace"><img src="https://agentmods.dev/badge/plugins/astro-han/claude-pace/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
claude-pace-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 4d 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": "claude-pace-marketplace",
"owner": {
"name": "yuhan",
"email": "[email protected]"
},
"metadata": {
"description": "Claude Pace statusline plugin marketplace",
"version": "0.9.4"
},
"plugins": [
{
"name": "claude-pace",
"source": {
"source": "github",
"repo": "Astro-Han/claude-pace",
"ref": "v0.9.4"
},
"description": "Lightweight statusline with quota pace tracking. Pure Bash + jq.",
"category": "monitoring",
"tags": [
"statusline",
"quota",
"usage",
"pace-tracking"
]
}
]
}
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.
- 4d ago First seen · 30 lines scan A e49addc83724
claude-pace-marketplace is a plugin published in the GitHub repository Astro-Han/claude-pace (229 stars, last pushed 1mo 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-30.
Other plugins, from other repositories
agmsg
Cross-agent messaging via SQLite. Send messages between CLI AI agents. No daemon, no network.
agent-messaging
Agent Messaging Protocol (AMP) - Secure, cryptographically signed messaging between AI agents across different providers.
branch-guard
Cut routine git/gh approval prompts: auto-approve safe commands (read-only, staging, branch/worktree create, feature-branch commits & pushes) and confirm protected-branch or destructive ones.
simple-statusline-marketplace
A minimal statusline for Claude Code.
email-leak-notice
Claude Code injects your account email into session context, where an agent may reuse it as a legitimate value and commit it. This warns once per session when a personal address appears in a tool payload. Never blocks.
bash-smart-approve
Auto-approves Claude Code Bash commands via AST-based allowlist. Handles pipes, subshells, compound commands, and env-var prefixes that literal Bash(...) prefix rules can't match.