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 rules/gtorreal/buda-mcp/marketplace-docs-syncgit clone --depth 1 https://github.com/gtorreal/buda-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/rules/gtorreal/buda-mcp/marketplace-docs-sync)<a href="https://agentmods.dev/rules/gtorreal/buda-mcp/marketplace-docs-sync"><img src="https://agentmods.dev/badge/rules/gtorreal/buda-mcp/marketplace-docs-sync.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 | $0.00000 | $0.00327 |
| Opus 5 | $0.00000 | $0.00163 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
marketplace-docs-sync 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 4d 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
Marketplace Documentation Sync
Any change to src/tools/ that adds, removes, or modifies a tool must be accompanied by matching updates to all three marketplace files.
Files to keep in sync
| File | What to update |
|---|---|
marketplace/claude-listing.md |
Add/remove/update ### \tool_name`` section |
marketplace/gemini-tools.json |
Add/remove/update entry in functionDeclarations[] with Gemini types (STRING, INTEGER, NUMBER, OBJECT) |
marketplace/openapi.yaml |
Add/remove/update path + response schema — public tools only (auth tools are excluded intentionally) |
When each file needs updating
- New tool added → add to all applicable files above
- Tool removed → remove from all files
- Parameter added/changed/removed → update description and
requiredarray in all files - Tool description changed → update all files
Quick checklist before committing
-
claude-listing.mdreflects all public tools (rungrep "^### \" marketplace/claude-listing.md | wc -l` to count) -
gemini-tools.jsonfunctionDeclarationscount matches -
openapi.yamlpaths count matches public tool count -
CHANGELOG.mdhas an entry describing the change
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.
- 4d ago First seen · 31 lines · 0 tokens per session scan A 1ffcb7e6d95b
marketplace-docs-sync is a cursor rule published in the GitHub repository gtorreal/buda-mcp (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 327 tokens. 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.