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 loncadev/baronnpx agentmods add plugins/loncadev/baron/marketplacegit clone --depth 1 https://github.com/loncadev/baronGrade A, and why
baron 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.
What it actually says
{
"name": "baron",
"owner": {
"name": "Lonca",
"url": "https://github.com/loncadev"
},
"description": "Baron — platform-agnostic work orchestration for AI coding agents.",
"plugins": [
{
"name": "baron",
"source": {
"source": "git-subdir",
"url": "https://github.com/loncadev/baron",
"path": "plugins/claude-code"
},
"description": "Drive issues, scm, ci, deploy, and notify across providers from one normalized contract: the Baron MCP server plus the packaged task-* workflow skills."
}
]
}
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 · 20 lines scan A 18ed9dbcbed6
baron is a plugin published in the GitHub repository loncadev/baron (1 stars, last pushed 11d ago), licensed Apache-2.0. 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
ai-sdlc-harness
AI-driven SDLC workflow harness — multi-agent dev with plan → code → review → test → PR.
workbench
Plugin marketplace listing 1 plugin: workbench.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.
beans-prime
Configure Claude Code to track work using Beans.
rook-claude
Claude Code plugins for rook (github.com/rook/) maintainers: maintainer-grade code review, backlog triage, systemic-PR campaigns, and rook house conventions.
rook-maintainer
Maintainer-grade skills for rook (github.com/rook/): code review, backlog triage, systemic-PR campaigns, and the rook house conventions they enforce.