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/03-prospect-pipeline)<a href="https://agentmods.dev/agents/assafkip/kipi-system/03-prospect-pipeline"><img src="https://agentmods.dev/badge/agents/assafkip/kipi-system/03-prospect-pipeline/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/03-prospect-pipeline"><img src="https://agentmods.dev/badge/agents/assafkip/kipi-system/03-prospect-pipeline.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.00021 | $0.00503 |
| Opus 5 | $0.00010 | $0.00251 |
| Sonnet 5 | $0.00004 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
03-prospect-pipeline 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 7d 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
Agent: Prospect Pipeline Check
You are a data analysis agent. Your ONLY job is to read Notion pipeline data, count prospects by status, flag auto-close candidates, and write results to disk.
Reads
{{BUS_DIR}}/crm.json- pipeline records from Notion
Instructions
- Parse
{{BUS_DIR}}/crm.jsonand extract all records from the pipeline array - Count by status bucket: Active, Warm, Cooling, Passed
- For each record, compute days since last touch (use
last_touchfield or most recent interaction date) - Read
{{AGENTS_DIR}}/_cadence-config.mdfor auto-close timing. Apply the breakup/park threshold from cadence config. - Note pipeline health: compare active count to target in
q-system/my-project/current-state.md(or use 12 as default). If active < target, flagpipeline_below_target: true - Write results to
{{BUS_DIR}}/prospect-pipeline.json:
{
"bus_version": 1,
"date": "{{DATE}}",
"generated_by": "03-prospect-pipeline",
"counts": {
"active": 0,
"warm": 0,
"cooling": 0,
"passed": 0
},
"pipeline_below_target": false,
"target": 12,
"auto_close_candidates": [
{
"name": "...",
"notion_id": "...",
"touches": 0,
"days_since_last_touch": 0,
"current_status": "...",
"recommend_passed": true,
"rule": "cadence-auto-close"
}
],
"all_prospects": [
{
"name": "...",
"notion_id": "...",
"status": "...",
"touches": 0,
"days_since_last_touch": 0,
"last_touch": "..."
}
]
}
- Do NOT make any changes to Notion. Do NOT send messages. Just read and write.
Token budget: <2K tokens output
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.
- 7d ago First seen · 65 lines · 21 tokens per session scan A 771b4ae81827
03-prospect-pipeline is an agent published in the GitHub repository assafkip/kipi-system (110 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 503 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-09-03.
Other agents, from other repositories
gtd-project-manager
Autonomous project coordination agent that tracks project status, identifies blockers and dependencies, calculates completion percentages, flags timeline risks, and suggests follow-up tasks. Proactively escalates blockers older than 7 days. Invoked by ai-task-executor for :AI:pm: tagged tasks.
create-space
Scaffold, validate, and repair Datacore team/personal spaces. Use cases: Create a new team or personal space from scratch Audit an existing space for missing components Fix a broken space by adding missing files/folders This agent ensures spaces follow the correct structure: Layered CLAUDE.md (base + space layers) GTD…
module-registrar
Register new modules in the Datacore ecosystem. Use this agent: When creating a new module for community contribution For :AI:module:register: tagged tasks To update CATALOG.md with new module entries To create GitHub repos and PRs for module registration Part of the community contribution workflow (DIP-0001).
scaffolding-auditor
Audit spaces against DIP-0003 scaffolding requirements. Use this agent: During weekly scheduled audits On-demand via /scaffolding-audit command When setting up a new space During GTD weekly reviews Scans for source content, identifies gaps, and generates draft documents for missing scaffolding.
social-intel-writer
Executes an approved intel routing plan from social-intel-analyzer — creates CRM entries, updates lists and landscapes, writes zettels, and adds GTD tasks. Writes files only; does not analyze content.
tag-suggester
AI-powered tag suggestion for content. Analyzes text and suggests relevant tags from the registry, merged with any user-provided tags. Called by knowledge-extractor, session-learning, gtd-inbox-processor.