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/moontzai/folderbridge-mcp/codebase-designnpx skills add MoonTzai/folderbridge-mcp --skill codebase-designgit clone --depth 1 https://github.com/MoonTzai/folderbridge-mcpWhat 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.00015 | $0.00232 |
| Opus 5 | $0.00008 | $0.00116 |
| Sonnet 5 | $0.00003 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
codebase-design 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 yesterday.
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
Codebase Design — FolderBridge Adaptation
Use this when the problem is where a module's interface or seam should live, not merely how a function should be written.
Think in these terms: module is anything with an interface plus implementation; interface is everything callers must know, including invariants and failure modes; depth is how much useful behavior the implementation hides relative to interface complexity; a seam is a place where behavior can change without callers changing; an adapter translates another interface into that seam; leverage is benefit per fact callers must learn; locality keeps related decisions together.
Prefer deep modules: small stable interfaces that own substantial policy. Use the deletion test: if deleting a proposed module merely scatters the same knowledge across callers, the module was providing leverage; if deletion barely changes what callers must know, it may be shallow ceremony.
Treat the interface as the durable test surface. One adapter can justify a hypothetical seam; two independent adapters are stronger evidence the seam is real.
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.
- yesterday First seen · 15 lines · 15 tokens per session scan A 63e8f4066bc4
codebase-design is a skill published in the GitHub repository MoonTzai/folderbridge-mcp (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 232 once invoked, about $0.0001 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
erga-mcp
Use immediately when a user shares a job-posting URL—including a bare link or chat preview—and when organizing recruiting records, evaluating career evidence, or proposing a truthful résumé update through Erga MCP.
mem0-tour
Browses all stored memories grouped by category with full content display. Use when reviewing all project memories, exploring stored knowledge, onboarding to a project, or getting an overview of captured decisions, conventions, and learnings.
mem0-vercel-ai-sdk
Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also…
stats
Displays memory usage statistics for the current session and project including counts by category, age distribution, and API latency. Use when checking how many memories exist, reviewing session activity, or auditing memory distribution across categories.
mem0-remember
Stores a memory verbatim from user input with appropriate type classification and metadata. Use when the user says remember this, save this, store this, note that, or explicitly asks to record a decision, preference, convention, or learning.
status
Diagnoses Mem0 connectivity, API key validity, and memory read/write functionality. Use when memory operations fail, searches return empty, or to verify the plugin is working correctly.