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 ahardin13/review-assistantnpx agentmods add plugins/ahardin13/review-assistant/marketplacegit clone --depth 1 https://github.com/ahardin13/review-assistantWrote 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/ahardin13/review-assistant/marketplace)<a href="https://agentmods.dev/plugins/ahardin13/review-assistant/marketplace"><img src="https://agentmods.dev/badge/plugins/ahardin13/review-assistant/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ahardin13 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 5d 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": "ahardin13",
"owner": {
"name": "Andy Hardin",
"handle": "ahardin13"
},
"plugins": [
{
"name": "review-assistant",
"description": "Interactive, human-in-the-loop PR review assistant",
"source": {
"source": "url",
"url": "https://github.com/ahardin13/review-assistant.git"
},
"version": "0.3.3"
}
]
}
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.
- 5d ago First seen · 19 lines scan A 7051b6eee358
ahardin13 marketplace is a plugin published in the GitHub repository ahardin13/review-assistant (3 stars, last pushed 3mo 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.
Other plugins, from other repositories
han-communication
Foundational communication plugin for the Han suite. Owns the canonical readability standard, the writing-voice profile, and the explanation standard for talking to a reader who will not implement the work, plus the readability-guidance skill that surfaces the first two into a calling skill's own context for in-voice…
handbook-agent-spec-kit
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation.
go-ultimate
Opinionated Go development skill — architecture, conventions, production readiness, repo/CI hygiene, review, and MCP/agent patterns.
claude-code
Meta-tools for Claude Code configuration and customization.
rails-consultant marketplace
Plugin marketplace listing 1 plugin: rails-consultant.
rails-consultant
A collection of skills for Rails development and consulting, with an emphasis on learning, communication, and client success.