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.
git clone --depth 1 https://github.com/trustxai/airbyte-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/trustxai/airbyte-mcp/conventional-commits)<a href="https://agentmods.dev/rules/trustxai/airbyte-mcp/conventional-commits"><img src="https://agentmods.dev/badge/rules/trustxai/airbyte-mcp/conventional-commits/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/trustxai/airbyte-mcp/conventional-commits"><img src="https://agentmods.dev/badge/rules/trustxai/airbyte-mcp/conventional-commits.svg" alt="Reviewed on agentmods" width="80" 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.00279 | $0.00279 |
| Opus 5.5 | $0.00112 | $0.00112 |
| Sonnet 5.5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
conventional-commits 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 1mo 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
Conventional Commits
All commit messages MUST follow Conventional Commits:
<type>[optional scope]: <description>
Types and when to use them
| Type | When | Triggers release? |
|---|---|---|
feat: |
New feature or capability | Yes (patch while pre-1.0) |
fix: |
Bug fix | Yes (patch) |
docs: |
Documentation only | No |
chore: |
Maintenance, deps, CI config | No |
refactor: |
Code change that neither fixes nor adds | No |
test: |
Adding or updating tests | No |
Examples
feat: add airbyte_get_stream_properties tool
fix: handle 401 during token exchange retry
docs: update endpoints checklist with streams
chore: bump mcp sdk to 1.28
feat!: rename all tool prefixes to ab_
Breaking changes
Append ! after the type or add BREAKING CHANGE: in the footer. While pre-1.0, this bumps minor (e.g. 0.1.1 → 0.2.0).
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.
- 1mo ago First seen · 38 lines · 279 tokens per session scan A 5e9528211587
conventional-commits is a cursor rule published in the GitHub repository trustxai/airbyte-mcp (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 279 tokens to every session, about $0.0011 per session on Opus 5.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 cursor rules, from other repositories
git-workflow
Vollagentische Entwicklung, Auto-Commits, Commit-Konventionen.
development-workflow
Cursor rule "development-workflow" from floriscornel/todo-mcp, covering development workflow for todo mcp, testing & quality assurance, commit structure, branch & pr workflow and publication & releases.
windsurfrules
Pare wraps CLI tools in MCP servers returning structured JSON. Always prefer Pare MCP tools over raw CLI.
single-commit-pr
Pull requests have exactly one commit: squash before opening, amend and force-push after.
commit-pattern
Conventional Commits, message format, and pre-commit analysis (local hook + checks).
pr-automation
Cursor rule "pr-automation" from floriscornel/todo-mcp, covering pull request guidelines, pre-pr checklist, pr description template, summary and changes.