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 josstei/argus-claudenpx agentmods add plugins/josstei/argus-claude/marketplacegit clone --depth 1 https://github.com/josstei/argus-claudeWrote 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/josstei/argus-claude/marketplace)<a href="https://agentmods.dev/plugins/josstei/argus-claude/marketplace"><img src="https://agentmods.dev/badge/plugins/josstei/argus-claude/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
argus-claude 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": "argus-claude",
"description": "Multi-agent code quality and architecture review with cross-validation",
"owner": {
"name": "josstei"
},
"plugins": [
{
"name": "argus",
"description": "Multi-agent code quality and architecture review with cross-validation",
"source": {
"source": "github",
"repo": "josstei/argus-claude",
"ref": "main"
},
"version": "1.0.0"
}
]
}
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 · 20 lines scan A d928f735be9a
argus-claude marketplace is a plugin published in the GitHub repository josstei/argus-claude (6 stars, last pushed 6mo 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
brooks-lint
AI code reviews grounded in twelve classic engineering books — decay risk diagnostics with book citations, severity labels, and six analysis modes (PR review, architecture audit, tech debt, test quality, health dashboard, full-sweep auto-fix).
dhpk
Reusable Claude Code harness with role-based agents, routed commands, sentinel-driven review hooks, opt-in PHP, Yii, PHPUnit, Laravel, JavaScript, Python, React, Next.js, and iOS/Swift modules, plus a parallel Codex CLI projection.
plumb-line
plumb-line provenance: epistemic honesty enforced by tooling. Five skills give any repository a clear source-truth layer, visible uncertainty, quarantined fakery, reproducible outputs, and rules enforced by machines rather than goodwill. New here? Run plumb-line-adopt first — it looks at your repo and tells you which…
onboard
Legacy project onboarding for Claude Code — analyzes the codebase, generates a token-budgeted CLAUDE.md, wires 4 guard hooks, manages forbidden zones, and aligns CI with local commands. Default --local-only writes zero PROJECT files (no team pollution). Use when setting up Claude Code on a legacy project, configuring.
handbook-agent-spec-kit
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation.
rails-consultant marketplace
Plugin marketplace listing 1 plugin: rails-consultant.