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.
git clone --depth 1 https://github.com/existential-birds/beagleWrote 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/existential-birds/beagle/beagle-core)<a href="https://agentmods.dev/plugins/existential-birds/beagle/beagle-core"><img src="https://agentmods.dev/badge/plugins/existential-birds/beagle/beagle-core/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/existential-birds/beagle/beagle-core"><img src="https://agentmods.dev/badge/plugins/existential-birds/beagle/beagle-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
beagle-core 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 1mo 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-core",
"description": "Shared code review workflows, verification protocol, git commands, and feedback handling. Recommended as a base for all beagle plugins.",
"version": "1.9.0",
"author": {
"name": "Existential Birds, LLC",
"email": "[email protected]"
},
"repository": "https://github.com/existential-birds/beagle",
"keywords": [
"code-review",
"verification",
"git",
"feedback",
"llm-artifacts",
"subagent-prompt",
"orchestration"
]
}
What it installs
The manifest is a name and a version. 19 skills travel with it, and installing the plugin installs all of them — 766 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill review-llm-artifacts A 101 tokens
- Skill review-structure A 48 tokens
- Skill fetch-pr-feedback A 17 tokens
- Skill fix-llm-artifacts A 43 tokens
- Skill gen-release-notes A 14 tokens
- Skill receive-feedback A 37 tokens
- Skill review-feedback-schema A 27 tokens
- Skill review-plan A 21 tokens
- Skill review-verification-protocol A 28 tokens
- Skill verify-llm-artifacts A 71 tokens
- Skill respond-pr-feedback A 15 tokens
- Skill llm-artifacts-detection A 56 tokens
- Skill review-skill A 45 tokens
- Skill review-skill-improver A 35 tokens
- Skill commit-push A 13 tokens
- Skill create-pr A 11 tokens
- Skill prompt-improver A 36 tokens
- Skill subagent-prompt A 116 tokens
- Skill skill-builder A 32 tokens
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.
- 1mo ago First seen · 20 lines scan A 596e578a3837
beagle-core is a plugin published in the GitHub repository existential-birds/beagle (84 stars, last pushed 1mo 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
developer-essentials
Essential developer skills including Git workflows, SQL optimization, error handling, code review, E2E testing, authentication, debugging, and monorepo management.
git-pr-workflows
Git workflow automation, pull request enhancement, and team onboarding processes.
codebase-cleanup
Technical debt reduction, dependency updates, and code refactoring automation.
diffctx
Selects the minimum code an LLM needs to review a git diff.
ci-review
CI-optimized code review: multi-agent parallel review with confidence scoring and atomic GitHub PR review posting via gh api.
workflow
Code review and worktree workflow commands.