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/tddnpx skills add MoonTzai/folderbridge-mcp --skill tddgit 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.00019 | $0.00226 |
| Opus 5 | $0.00010 | $0.00113 |
| Sonnet 5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
tdd 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 2d 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
Test-Driven Development — FolderBridge Adaptation
Drive one observable behavior at a time through a public interface seam.
For each vertical slice: write one test that names a behavior from the spec, run it and confirm it is red for the intended reason, implement only enough behavior to turn it green, then refactor while the suite remains green. Do not batch a large imagined test suite before implementation; each passing slice should teach you what the next slice actually needs.
Prefer tests that survive internal renames and implementation changes. Assert literal outcomes from the requirement rather than recomputing expected values with the same algorithm as production. Use a seam that callers naturally cross; if the only way to test is by reaching deep into internals, reconsider the module design first.
Run the smallest relevant test frequently and the full suite at meaningful checkpoints. Never refactor while the target behavior is still red. When a regression is being fixed, keep the red test as a permanent guard unless it only tests incidental implementation detail.
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.
- 2d ago First seen · 15 lines · 19 tokens per session scan A 7017e56fc5eb
tdd is a skill published in the GitHub repository MoonTzai/folderbridge-mcp (0 stars, last pushed 2d ago), licensed Apache-2.0. It adds 19 tokens to every session and 226 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
mem0-integrate
Integrate Mem0 into an existing repository using a goal-driven, TDD pipeline. Detects the repo's language automatically and asks the user to pick between Mem0 Platform (managed) and Mem0 Open Source (self-hosted). Writes failing tests before any implementation. Produces a local feature branch plus .mem0-integration/…
seller-research
Use when researching a merchant, storefront, marketplace seller, or merchant of record for a buying decision, especially when identity, refund terms, fulfillment, counterfeit risk, domain history, or independent buyer outcomes are uncertain.
engineering-workflow
可靠工程工作流的执行细则——探索→计划→TDD→系统化调试→代码审查→完成前验证。供方法论教练在开发任务中逐步引导。.
product-research
Use when researching or comparing a specific product, model, or variant for a buying decision, especially when specifications conflict, fit or compatibility matters, retailer copy dominates, or the evidence may be incomplete.
codexless-release-supervisor
Prepare, validate, and publish Codexless preview/hotfix releases from the canonical household source, including acceptance anti-omission gates, candidate provenance/parity, manifest/build identity, native Windows/macOS fresh-install acceptance from clean public source, safe Git integration, GitHub prerelease…
codexless-browser-repair
Diagnose and temporarily repair Codexless Browser compatibility after a Codex, Chrome Skill, or Browser runtime update when Codexless Browser stopped working. Use for current-version Codexless Browser compatibility drift, not ordinary website bugs, general Browser operation, Codexless install/update work, or long-term…