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/datahub-project/datahub-skillsWrote 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/commands/datahub-project/datahub-skills/connector-review)<a href="https://agentmods.dev/commands/datahub-project/datahub-skills/connector-review"><img src="https://agentmods.dev/badge/commands/datahub-project/datahub-skills/connector-review/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/commands/datahub-project/datahub-skills/connector-review"><img src="https://agentmods.dev/badge/commands/datahub-project/datahub-skills/connector-review.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.00013 | $0.00141 |
| Opus 5 | $0.00006 | $0.00071 |
| Sonnet 5 | $0.00003 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
connector-review 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 11d 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
DataHub Connector PR Review
Use the Skill tool to invoke the full datahub-connector-pr-review skill:
Skill tool:
skill: "datahub-skills:datahub-connector-pr-review"
User's request: $ARGUMENTS
This skill reviews connector code against the 22 DataHub standards. On Claude Code with pr-review-toolkit installed, it runs 5 review agents in parallel. Otherwise it performs the same checks sequentially.
If no arguments provided, ask which connector to review.
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.
- 11d ago First seen · 21 lines · 13 tokens per session scan A ecab35496bef
connector-review is a command published in the GitHub repository datahub-project/datahub-skills (38 stars, last pushed 13d ago), licensed Apache-2.0. It adds 13 tokens to every session and 141 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-30.
Other commands, from other repositories
evaluate-connector
Evaluate a Fivetran connector for correctness, SDK compliance, security, and reliability.
review-rust
Focused Rust/Tauri backend review with rust-backend-architect (Primary Owner).
api-style-review
Review SAP API style compliance for REST, OData, OpenAPI, SDK naming, documentation, and lifecycle readiness.
fec-doc-sync
Sync README, docs, environment variables, scripts, API/routing/component descriptions and deployment instructions from code and project sources of truth.
document
On-demand documentation generation — API docs, architecture updates, user guides.
api-review
Review the current code or API against API design principles — identifies violations and suggests improvements.