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/alphabravo-oss/guildWrote 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/alphabravo-oss/guild/holmes)<a href="https://agentmods.dev/plugins/alphabravo-oss/guild/holmes"><img src="https://agentmods.dev/badge/plugins/alphabravo-oss/guild/holmes/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/alphabravo-oss/guild/holmes"><img src="https://agentmods.dev/badge/plugins/alphabravo-oss/guild/holmes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
holmes 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": "holmes",
"description": "Macro-architecture / design-cohesion review — the senior-engineer 'is this shaped right or accreted?' critique, not bug-hunting or lint. Reads a codebase like Holmes reads a room: deduces the real design problem from the detail that's out of place. /holmes:review <target> runs a Workflow engine that builds a grounded structural map of the target (a path, the diff, a subsystem, or a described piece of logic), then runs 7 blind design lenses — package/module proliferation, missed sharing & reuse, helper sprawl & abstraction fit, flow & layering, cohesion, naming/structural consistency, accretion markers — each a separate agent hunting one class of design problem. Every candidate finding is adversarially verified by a skeptic that tries to refute it as intentional, so plausible-but-wrong smells get dropped; a completeness critic then re-lenses any in-scope area no finding touched. The result is synthesized into a per-subsystem deliberate/mixed/accreted verdict with file:line evidence and an ordered, concrete reshaping plan. Report only — never edits code. Forbidden from style nits, correctness bugs, or treating comments as source of truth ('everybody lies'); an empty result is a valid honest outcome for a well-shaped target.",
"version": "0.1.0",
"author": {
"name": "AlphaBravo"
}
}
What it installs
The manifest is a name and a version. 1 command travel with it, and installing the plugin installs all of them — 30 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 9 lines scan A 584f0cb70c7b
holmes is a plugin published in the GitHub repository alphabravo-oss/guild (2 stars, last pushed 11d 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-09-04.
Other plugins, from other repositories
han-communication
Foundational communication plugin for the Han suite. Owns the canonical readability standard, the writing-voice profile, and the explanation standard for talking to a reader who will not implement the work, plus the readability-guidance skill that surfaces the first two into a calling skill's own context for in-voice…
pedantic-coder
Zero-tolerance code pedantry — naming precision, casing law, structural symmetry, import discipline, and the obsessive details that separate clean code from correct code.
ai-infra-auto-driven-skills
Agent-ready playbooks for LLM serving benchmarks, SGLang model Day-0 support, capacity planning, profiling, code review, incidents, PR-history dossiers, and SGLang PR/article explainer videos.
git-pr
Committing, PR creation and review triage, and dependency upgrades.
code-quality
OxLint, Biome, and Prettier configuration, linting skills, and pre-commit hooks for consistent code quality.
coderabbit
CodeRabbit integration for Claude Code - local code review and PR comment management.