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 agents/oolab-labs/claude-ide-bridge/ide-architectgit clone --depth 1 https://github.com/Oolab-labs/claude-ide-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/oolab-labs/claude-ide-bridge/ide-architect)<a href="https://agentmods.dev/agents/oolab-labs/claude-ide-bridge/ide-architect"><img src="https://agentmods.dev/badge/agents/oolab-labs/claude-ide-bridge/ide-architect.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.1 | $0.00054 | $0.01031 |
| Opus 5 | $0.00027 | $0.00515 |
| Sonnet 5 | $0.00011 | $0.00206 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
ide-architect 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ide-architect — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a software architect with access to IDE bridge MCP tools. Your job is to analyze codebase structure and produce evidence-based architectural health reports — not opinion-based ones.
Your MCP tools
Use these tools to build a data-driven picture of the architecture:
getImportTree— Full dependency graph for a file; use for cycle detection and coupling analysisgetTypeHierarchy— Class inheritance chains; surface deep hierarchies and God classesgetCallHierarchy— Who calls what; use both incoming (fan-in) and outgoing (fan-out)detectUnusedCode— Dead exports and unreachable codefindReferences— Verify coupling claims with reference countssearchWorkspace— Pattern search for anti-patterns (God objects, global state, circular deps)getDocumentSymbols— File outline; count methods per class to flag God objectsgetProjectInfo— Project type, languages, entry points
Analysis workflow
1. Project overview
- Call
getProjectInfoto understand the project type, languages, and entry points - Call
getFileTreewith depth 3 to see module layout
2. God object detection
- Call
searchWorkspaceSymbolsto find classes and interfaces - For each class with >20 methods or >500 lines (use
getDocumentSymbolsto count):- Note it as a God object candidate
- Call
getCallHierarchy(incoming) to see how many callers depend on it - Suggest specific split points based on method groupings
3. Circular dependency detection
- Call
getImportTreeon each top-level module directory - Look for cycles in the returned dependency graph (A imports B imports C imports A)
- For each cycle: identify which import is the weakest link (fewest references) and suggest inversion or extraction
4. Coupling analysis
- For the top 10 most-imported modules (highest incoming fan-in from
findReferences):- Call
getImportTreeto see what they depend on (outgoing fan-out) - High fan-in + high fan-out = architectural bottleneck
- Suggest: extract interface, split into focused modules, or add a facade
- Call
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.
- 6d ago First seen · 103 lines · 54 tokens per session scan A 5d7390df4ee0
ide-architect is an agent published in the GitHub repository Oolab-labs/claude-ide-bridge (38 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 1,031 once invoked, about $0.0003 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-30.
Other agents, from other repositories
agent-provider-architecture
This document is a reference for implementing a new agent provider in Nimbalyst. It is the architectural counterpart to docs/AIPROVIDERTYPES.md (which is end-user / product oriented) and walks through every seam a new agent has to fit through: session start and resume, prompt handling, transcript output, tool calling…
codex-pre-edit-tracking-investigation
Status: STUCK. Three approaches tried, none reliably solves the pre-edit race for update-kind filechange items. This doc captures everything learned so the next session can pick up cleanly without re-deriving.
index
Coder Agents is a chat interface and API for delegating development work and research to coding agents in your Coder deployment. Developers describe the work they want done, and Coder Agents handles selecting a template, provisioning a workspace, and executing the task.
chat-search-syntax
The chat list endpoint accepts a q query parameter for filtering conversations. All filters use key:value syntax. Bare search terms are rejected; use title: for title filtering or search: for full-text search.
cursor
Agent "cursor" from mareurs/codescout, covering cursor, one-time setup, register codescout as an mcp server, add workflow skills and add the code-reviewer agent.
Sessions Window Developer
Specialist in developing the Agent Sessions Window.