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 skills add MoonTzai/folderbridge-mcp --skill implementgit clone --depth 1 https://github.com/MoonTzai/folderbridge-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/moontzai/folderbridge-mcp/implement)<a href="https://agentmods.dev/skills/moontzai/folderbridge-mcp/implement"><img src="https://agentmods.dev/badge/skills/moontzai/folderbridge-mcp/implement.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.00017 | $0.00195 |
| Opus 5 | $0.00009 | $0.00097 |
| Sonnet 5 | $0.00003 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
implement 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.
What it actually says
Implement — FolderBridge Adaptation
Use this only after the requested behavior and important seams are already settled. Do not reopen product/design questions without evidence that the agreed design is impossible or unsafe.
Execute the plan in small vertical slices. Use TDD where the behavior has a stable observable seam. Run focused tests frequently and the full regression suite before declaring completion. Keep type/static checks in the loop when the project has them.
Track deviations from the spec explicitly: either correct the implementation or update the design with a reason. Do not silently broaden scope.
When implementation is green, perform a code-review pass against both repository standards and the originating design/spec. Resolve supported high/medium findings, rerun the suite, and leave the worktree/diff in an auditable state. Version/build/publish actions are separate explicit steps unless the user's request already includes them.
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 · 15 lines · 17 tokens per session scan A 9fa74267691a
implement is a skill published in the GitHub repository MoonTzai/folderbridge-mcp (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 195 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
cli-command
Design, implement, or review Composio CLI commands under ts/packages/cli using Effect, @effect/cli, services, output conventions, configuration and environment variables, and local vendor references. Use for CLI command UX, command wiring, service changes, or CLI source edits. Do not use for CLI E2E-only work; use…
python-testing
Test Python applications with pytest fixtures, parametrization, temporary paths, and regression coverage.
rel-ai-verification
Use after repository changes, fixes, or release work when the task needs proof of completion, including targeted regression checks, final verification, release readiness, completion audits, or confirmation that implemented behavior works. Do not use for open-ended architecture or feasibility investigation before…
quality
PALADIN quality gatekeeper. Two-stage system: Stage 1 checks spec compliance (pass/fail, blocks everything on failure). Stage 2 scores project health 0-100 across 6 tiers. Issues verdict: SHIP IT / SHIP WITH CAUTION / NOT READY / BLOCKED. Evidence Before Claims: every finding must cite the file, line, and what was…
review
Challenge a Hardproof implementation during REVIEW against its approved contract, code quality, tests, and risk boundaries.
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.