Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add chrismdemian/claude-code-discord-bridge/plugin install discord-bridgeWrote 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/skills/chrismdemian/claude-code-discord-bridge/status)<a href="https://agentmods.dev/skills/chrismdemian/claude-code-discord-bridge/status"><img src="https://agentmods.dev/badge/skills/chrismdemian/claude-code-discord-bridge/status/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/skills/chrismdemian/claude-code-discord-bridge/status"><img src="https://agentmods.dev/badge/skills/chrismdemian/claude-code-discord-bridge/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00010 | $0.00196 |
| Opus 5 | $0.00005 | $0.00098 |
| Sonnet 5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
status scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:${BRIDGE_PORT:-7676}/health What it actually says
Discord Bridge Status
Check the health and status of the Discord bridge.
Steps
-
Check if the bridge service is running:
curl -s http://localhost:${BRIDGE_PORT:-7676}/health -
Check if pm2 is managing the bridge:
npx pm2 status discord-bridge -
Report the results to the user:
- Bridge status (running / not running)
- Discord connection (connected / disconnected)
- Number of active sessions
- Uptime
- If not running, suggest:
npx pm2 start ${CLAUDE_PLUGIN_ROOT}/bridge/index.ts --name discord-bridge --interpreter bun
-
If the bridge is not running and the user hasn't set up yet, suggest running
/discord-bridge:setup.
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.
- 10d ago First seen · 30 lines · 10 tokens per session scan A 5b699e9aa7d4
status is a skill published in the GitHub repository chrismdemian/claude-code-discord-bridge (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 196 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
goclaw
Use this skill when administering, operating, or debugging a GoClaw gateway through the GoClaw CLI/runtime package. It covers CLI discovery, safe command inspection, gateway health/config diagnostics, agents, skills, MCP/tools, runtime packages, credentials, traces, sessions, channels, providers, cron/jobs, and…
discord-troubleshooting
Troubleshoots and resolves gemini-discord bot connection, gateway issues (e.g. fatal disconnects 4014, 4004), and port conflicts. Ensures the bot gets online and operational by running loops to verify success.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
ha-logs
A read-only troubleshooting skill for querying Hope Agent’s local SQLite databases, which store logs, conversations, and background-job status.