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/brilliantdirectories/brilliant-directories-mcpWrote 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/brilliantdirectories/brilliant-directories-mcp/brilliant-directories-mcp)<a href="https://agentmods.dev/plugins/brilliantdirectories/brilliant-directories-mcp/brilliant-directories-mcp"><img src="https://agentmods.dev/badge/plugins/brilliantdirectories/brilliant-directories-mcp/brilliant-directories-mcp/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/brilliantdirectories/brilliant-directories-mcp/brilliant-directories-mcp"><img src="https://agentmods.dev/badge/plugins/brilliantdirectories/brilliant-directories-mcp/brilliant-directories-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bd 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 12d 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": "bd",
"version": "1.1.0",
"category": "productivity",
"description": "Brilliant Directories integration. Manage members, posts, leads, reviews, web pages, redirects, email templates, forms, menus, tags, widgets, and post-type configurations on any Brilliant Directories website via the public hosted MCP at brilliantmcp.com. Bundles growth-automation skills (/bd:events researches local events and creates SEO-rich event posts; more skills coming).",
"author": {
"name": "Brilliant Directories",
"url": "https://github.com/brilliantdirectories"
},
"homepage": "https://www.brilliantdirectories.com",
"repository": "https://github.com/brilliantdirectories/brilliant-directories-mcp",
"license": "MIT",
"keywords": [
"brilliant-directories",
"membership",
"directory",
"mcp",
"model-context-protocol",
"cms",
"crm"
]
}
What it installs
The manifest is a name and a version. 2 skills, 2 MCP servers travel with it, and installing the plugin installs all of them — 188 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 23 lines scan A 285489e8cdf8
bd is a plugin published in the GitHub repository brilliantdirectories/brilliant-directories-mcp (18 stars, last pushed 4d 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
avoid-ai-writing
Audit and rewrite prose that reads as machine-generated, across READMEs, changelogs, PR descriptions, docs, and blog copy, with detect-only, rewrite, and edit-in-place modes.
accessibility-compliance
WCAG accessibility auditing, compliance validation, UI testing for screen readers, keyboard navigation, and inclusive design.
agent-teams
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams.
api-scaffolding
REST and GraphQL API scaffolding, framework selection, backend architecture, and API generation.
application-performance
Application profiling, performance optimization, and observability for frontend and backend systems.
arm-cortex-microcontrollers
ARM Cortex-M firmware development for Teensy, STM32, nRF52, and SAMD with peripheral drivers and memory safety patterns.