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.
npx agentmods add skills/muchiny/bridge-mcp/discovernpx skills add muchiny/bridge-mcp --skill discovergit clone --depth 1 https://github.com/muchiny/bridge-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/skills/muchiny/bridge-mcp/discover)<a href="https://agentmods.dev/skills/muchiny/bridge-mcp/discover"><img src="https://agentmods.dev/badge/skills/muchiny/bridge-mcp/discover.svg" alt="Measured on agentmods" 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 | $0.00101 | $0.00387 |
| Opus 5 | $0.00051 | $0.00193 |
| Sonnet 5 | $0.00020 | $0.00077 |
| Haiku 4.5 | $0.00010 | $0.00039 |
Grade A, and why
discover 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 4d 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
Tool Discovery -- Progressive Exploration
Explore the 476 tools across 77 groups available in bridge-mcp.
No arguments -- show all groups
!bridge-mcp list-tools --groups-only
Ask which group interests the user, or suggest searching by keyword.
Group name provided
!bridge-mcp list-tools --group $ARGUMENTS
For each tool shown, the user can ask for details:
!bridge-mcp describe-tool <tool_name>
The describe-tool output includes a Reduction Strategy line at the top
telling you which params (jq_filter, columns, limit, etc.) apply for token-efficient output.
Search term provided
!bridge-mcp list-tools --search $ARGUMENTS
Tips for the user
- 77 groups: docker, kubernetes, systemd, networking, firewall, packages, users, cron, logs, files, etc.
- Token-efficient: always use
columns,limit, orjq_filterparams to reduce output - 9 protocols: SSH, WinRM, PSRP, Telnet, K8s Exec, Serial, AWS SSM, Azure, GCP
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.
- 4d ago First seen · 44 lines · 101 tokens per session scan A 69c9a989740b
discover is a skill published in the GitHub repository muchiny/bridge-mcp (8 stars, last pushed 4d ago), licensed MIT. It adds 101 tokens to every session and 387 once invoked, about $0.0005 per session on Opus 5. 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-31.
Other skills, from other repositories
eu-ai-act-compliance
EU AI Act compliance logging and requirements. Use this skill when ensuring transparency, human oversight, and record-keeping per Regulation (EU) 2024/1689 — even if they just say "add compliance logging" or "make sure this is EU AI Act compliant". Not for security-code-auditor, privacy-first.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.