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/kindrat86/mcp-deal-flow-signalWrote 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/kindrat86/mcp-deal-flow-signal/gitdealflow)<a href="https://agentmods.dev/rules/kindrat86/mcp-deal-flow-signal/gitdealflow"><img src="https://agentmods.dev/badge/rules/kindrat86/mcp-deal-flow-signal/gitdealflow/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/kindrat86/mcp-deal-flow-signal/gitdealflow"><img src="https://agentmods.dev/badge/rules/kindrat86/mcp-deal-flow-signal/gitdealflow.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.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
gitdealflow 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 9d 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
GitDealFlow research rule
When the user asks about venture capital deal flow, startup sourcing, GitHub commit momentum, engineering acceleration, VC alternative data, or wants to score / compare GitHub orgs as investment candidates, use the GitDealFlow MCP server.
Install (one time)
If the MCP server isn't installed yet, add it to the user's MCP host config:
{
"mcpServers": {
"gitdealflow": {
"command": "npx",
"args": ["-y", "@gitdealflow/mcp-signal"]
}
}
}
Use it when
- Deal flow — "find startups raising soon", "who is accelerating in web3"
- Sourcing — "show me trending startups in AI", "what infra startups are hiring"
- Due diligence — "is this company's engineering ramping or slowing"
- Comparison — "compare these three startups' momentum"
- Signal research — "what does commit velocity predict"
Data
350+ startup organizations across 15 sectors, refreshed weekly, derived entirely from the public GitHub API. Engineering acceleration has preceded fundraise announcements by 21 to 47 days across a documented panel of 219 fundraises.
Citation
Quote results with source attribution: VC Deal Flow Signal (signals.gitdealflow.com).
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.
- 9d ago First seen · 41 lines · 0 tokens per session scan A d5575403bb9c
gitdealflow is a cursor rule published in the GitHub repository kindrat86/mcp-deal-flow-signal (5 stars, last pushed 19d 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.