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 existential-birds/beaglenpx agentmods add plugins/existential-birds/beagle/beagle-analysisgit clone --depth 1 https://github.com/existential-birds/beagleGrade A, and why
beagle-analysis 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": "beagle-analysis",
"description": "Architecture analysis, brainstorming, ADR generation, LLM-as-judge comparison, and spec gap resolution.",
"version": "2.10.0",
"author": {
"name": "Existential Birds, LLC",
"email": "[email protected]"
},
"repository": "https://github.com/existential-birds/beagle",
"keywords": [
"12-factor",
"architecture",
"brainstorm-beagle",
"resolve-beagle",
"prfaq-beagle",
"write-plan",
"tdd-planning",
"implementation-plan",
"working-backwards",
"press-release",
"concept-filter",
"web-research",
"artifact-analysis",
"adr",
"llm-judge",
"analysis",
"strategy",
"strategic-planning",
"wardley-mapping",
"blue-ocean",
"porter-five-forces",
"mckinsey-7s",
"balanced-scorecard",
"competitive-analysis",
"business-strategy",
"strategy-review"
]
}
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 · 39 lines scan A 156500afcab7
beagle-analysis is a plugin published in the GitHub repository existential-birds/beagle (79 stars, last pushed 23d 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-30.
Other plugins, from other repositories
jenkins-cli
GitHub CLI-style interface for Jenkins controllers - create multibranch jobs, inspect config.xml, and manage runs, logs, artifacts, credentials, nodes, and queues.
shinkoku
確定申告を自動化する Claude Code Plugin。会社員＋副業（事業所得・青色申告）の所得税・消費税確定申告をエンドツーエンドで支援。.
taskbar-code
Task Bar Hero Code plugin marketplace.
trvl
Claude Code travel companion bundling the trvl MCP server, trip planning skills, price watches, destination research, and a multi-leg trip coordinator.
shotcut-mcp
Full transactional editor for Shotcut projects through a local MCP server.
promptline
Local, read-only visual timeline of your Claude Code prompt history - dashboard, activity heatmap, and searchable per-project/session feed. Binds to 127.0.0.1 only, no outbound network calls, nothing written back to /.claude.