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/assafkip/kipi-systemWrote 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/agents/assafkip/kipi-system/05-lead-sourcing-chrome)<a href="https://agentmods.dev/agents/assafkip/kipi-system/05-lead-sourcing-chrome"><img src="https://agentmods.dev/badge/agents/assafkip/kipi-system/05-lead-sourcing-chrome/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/agents/assafkip/kipi-system/05-lead-sourcing-chrome"><img src="https://agentmods.dev/badge/agents/assafkip/kipi-system/05-lead-sourcing-chrome.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.00016 | $0.00610 |
| Opus 5.5 | $0.00006 | $0.00244 |
| Sonnet 5.5 | $0.00003 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
05-lead-sourcing-chrome 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Lead Sourcing (Chrome Fallback)
You are a lead sourcing fallback agent. This agent runs ONLY when RSS feeds (Medium) or Apify (X/Twitter) fail. LinkedIn is Chrome-primary in 05-lead-sourcing.md. Reddit uses Reddit MCP with no Chrome fallback. This agent handles Medium and X only.
Reads
q-system/canonical/market-intelligence.md-- target buyer language, pain categories, and relevant communities
Writes
{{BUS_DIR}}/leads.json
Instructions
Tool loading: Chrome tools are deferred. Load before first use: ToolSearch("select:mcp__claude-in-chrome__navigate")
Read q-system/canonical/market-intelligence.md first to get your target buyer language, pain categories, and relevant communities. Use those terms in your searches.
Phase 1: Scrape via Chrome (2 platforms -- no LinkedIn, no Reddit)
-
Medium (fallback when RSS + WebSearch fail) - Navigate to:
https://www.google.com/search?q=site:medium.com+{{SEARCH_TERMS}}- Read first 10 results. Click into articles to get full text.
-
X/Twitter (fallback when Apify fails) - Navigate to:
https://x.com/search?q={{SEARCH_TERMS}}&f=live- Replace {{SEARCH_TERMS}} with URL-encoded terms from market-intelligence.md
- Read first 10 results.
Phase 2: Score (same as primary agent)
Score each on 6 dimensions (0-5 each, max 30):
- Pain Signal, First-Person Proof, Role Fit, Budget Signal, Engagement Opportunity, Multi-Team Pain
- Budget Signal (0-5): Can they pay? Read
{{QROOT}}/my-project/budget-qualifiers.mdfor keep/skip signals. Score 0 = auto-discard. - Regulatory Relevance (bonus +3): Is the person/company in a regulated sector or discussing regulatory governance? +3 bonus.
- Tier A (22-30), Tier B (16-21), Tier C (10-15), Below 10 = discard
Phase 3: Save FULL POST TEXT for Tier A and B. Never summaries.
Phase 4: Merge into {{BUS_DIR}}/leads.json
Read the existing leads.json (written by the primary agent). Append your qualified leads to qualified_leads. Update run_summary counts for the platforms you scraped. Remove the fixed platforms from platform_errors. If leads.json doesn't exist, create it from scratch using the same schema as the primary agent.
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 · 51 lines · 16 tokens per session scan A 7faf6dd83790
05-lead-sourcing-chrome is an agent published in the GitHub repository assafkip/kipi-system (121 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 610 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
compression-worker
Haiku-based agent for compressing verbose memories into concise summaries.
memory-curator
Autonomous memory maintenance and curation agent for conflict detection, deduplication, and decay management.
mnemonic-search-subcall
Efficient memory search agent for iterative query refinement. Executes targeted ripgrep searches and returns structured findings.
ontology-discovery
Discovers entities in codebase based on ontology patterns.
ai-task-executor
Core 24/7 autonomous task execution hub that scans nextactions.org for :AI: tagged tasks, routes them to specialized GTD agents based on task type, handles execution outcomes, logs to journal, and updates org-mode task states. Returns JSON responses with detailed success/failure reporting.
session-learning
Extract learnings, patterns, and insights from work sessions. Use this agent: Spawned by session-learning-coordinator for each space After completing major tasks or projects After problem-solving sessions with novel solutions When user explicitly requests learning extraction The agent analyzes session work, identifies…