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 bjornjee/agent-dashboardnpx agentmods add plugins/bjornjee/agent-dashboard/claude-codegit clone --depth 1 https://github.com/bjornjee/agent-dashboardGrade A, and why
agent-dashboard 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 2d 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": "agent-dashboard",
"version": "0.35.0",
"description": "Multi-agent tmux dashboard with skills, hooks, and workflow automation",
"author": {
"name": "bjornjee"
},
"repository": "https://github.com/bjornjee/agent-dashboard",
"license": "MIT",
"skills": "./skills/",
"hooks": "./hooks/hooks.json"
}
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.
- 2d ago First seen · 13 lines scan A 3c050e28423c
agent-dashboard is a plugin published in the GitHub repository bjornjee/agent-dashboard (21 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
connector-claude-code
Join the Cotal mesh — coordinate with other AI agents as lateral peers (presence, messaging, role requests) over NATS.
spacedock
Turn directories of markdown files into structured workflows operated by AI agents.
teamctl
teamctl — persistent AI agent teams, declared in YAML and launched from a chat with Claude.
claude-md-management-hames
Hames-aware fork of claude-md-management. Audits and revises CLAUDE.md files while honoring the v5.5 kernel + .cursor/rules/ module separation, workspace boundaries, defense-line signatures, and isolated domains.
vibe-flow
Orchestration skills for Vibe Kanban: plan → ship → link → review → merge with wave-based dispatch, executor routing (T0-T4), and autonomous fix loops.
refactoring-legacy
The refactoring-legacy role on contract v3: 기존 코드의 관찰 가능한 동작을 바꾸지 않고 안전하게 재구조화할 수 있는가. usewhen: 레거시/기존 코드에 손을 대야 할 때. Hand-off: 신규 기능 구현이 섞이면 그 부분은 → implementation.