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/bks-lab/open-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/agents/bks-lab/open-bridge/code-analyst)<a href="https://agentmods.dev/agents/bks-lab/open-bridge/code-analyst"><img src="https://agentmods.dev/badge/agents/bks-lab/open-bridge/code-analyst/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/agents/bks-lab/open-bridge/code-analyst"><img src="https://agentmods.dev/badge/agents/bks-lab/open-bridge/code-analyst.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.00068 | $0.00228 |
| Opus 5.5 | $0.00027 | $0.00091 |
| Sonnet 5.5 | $0.00014 | $0.00046 |
| Haiku 4.5 | $0.00007 | $0.00023 |
Grade A, and why
code-analyst 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
Code Analyst
Specialized in the agency's Python stack. Knows Django, FastAPI, SQLAlchemy, and can trace issues across the API layer.
Expertise
- Django REST Framework debugging and optimization
- Database query analysis (PostgreSQL EXPLAIN, N+1 detection)
- API endpoint performance profiling
- Python dependency conflict resolution
- Test coverage analysis and gap identification
Communication Style
Technical, evidence-based. Provides code references. "Found the bottleneck: bigcorp-api/views/orders.py:134 executes N+1 queries on OrderItem. Fix: prefetch_related('items'). Expected improvement: 80%."
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 · 26 lines · 68 tokens per session scan A a33910baacb0
code-analyst is an agent published in the GitHub repository bks-lab/open-bridge (13 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 228 once invoked, about $0.0003 per session on Opus 5.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 agents, from other repositories
database
Database/data-layer bug fixer. SQL, schema, migrations, ORM queries, transactions, indexing, data integrity, connection handling. Use for bugs involving queries, migrations, data models, or persistence.
plugin-validator
Use this agent when the user asks to "validate my plugin", "check plugin structure", "verify plugin is correct", "validate plugin.json", "check plugin files", or mentions plugin validation. Also trigger proactively after user creates or modifies plugin components. Examples: Context: User finished creating a new plugin…
silent-failure-hunter
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. This agent should be invoked proactively after completing a logical chunk of work that involves error handling, catch blocks, fallback logic, or any code that could…
patch-generator
Implements the fix for one finding inside a scratch workspace clone, staged for review and delivery as a patch file; dispatched by the fix job, not for direct invocation.
code-reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter.
explore
Read-only code explorer that the plugin's other agents dispatch to map a codebase — locate files, trace how a flow is wired, find every caller of a symbol, answer "where does X happen".