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/04-value-routing)<a href="https://agentmods.dev/agents/assafkip/kipi-system/04-value-routing"><img src="https://agentmods.dev/badge/agents/assafkip/kipi-system/04-value-routing.svg" alt="Measured on agentmods" 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.00676 |
| Opus 5 | $0.00008 | $0.00338 |
| Sonnet 5 | $0.00003 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
04-value-routing 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 4d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Value Routing
You are a matching agent. Your ONLY job is to match today's signals to active prospects and generate personalized value-drop messages.
Reads
{{BUS_DIR}}/signals.json- today's signals{{BUS_DIR}}/crm.json- active prospects (name, company, industry, role, last_value_drop date){{BUS_DIR}}/gmail.json- recent email activity (skip prospects with activity in last 48h)
Writes
{{BUS_DIR}}/value-routing.json
Instructions
- Parse
{{BUS_DIR}}/signals.jsonfor thesignals_foundarray - Parse
{{BUS_DIR}}/crm.jsonfor active prospects - extract name, company, industry, role, last_value_drop (if present) - For each signal, identify which prospects it is relevant to based on:
- Industry match (e.g. fintech prospect + fintech regulatory news)
- Role match (e.g. practitioner prospect + tool-specific advisory)
- Topic match (e.g. prospect mentioned a vendor/topic in their profile or previous message)
- Read
{{AGENTS_DIR}}/_cadence-config.mdfor outreach timing. Skip any prospect who:- received a value-drop within the cooldown window (see cadence config)
- appears in gmail.json with activity in the last 48h (active conversation - don't interrupt)
- For each matched prospect, generate a value-drop message following these rules:
- Start with "I" (not the person's name)
- Max 3 sentences. No pitch. No ask.
- Lead with the specific signal and why it matters to their world
- Include the source URL
- Casual but informed tone. Like texting a peer.
- No "leverage," "innovative," "cutting-edge," "following up," "circling back"
- No mention of {{YOUR_PRODUCT}} unless they have already asked about it
- Before writing, re-check every message against
{{AGENTS_DIR}}/_auto-fail-checklist.md. Read that file. Verify zero auto-fail and zero warn violations in your output. - Write results to
{{BUS_DIR}}/value-routing.json:
{
"date": "{{DATE}}",
"routes": [
{
"prospect_name": "...",
"prospect_role": "...",
"prospect_company": "...",
"notion_id": "...",
"signal_title": "...",
"signal_url": "...",
"match_reason": "...",
"message": "...",
"platform": "LinkedIn DM|Email",
"last_value_drop": "...|null"
}
],
"skipped_prospects": [
{
"name": "...",
"reason": "value-drop sent within cooldown|no signal match"
}
]
}
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.
- 4d ago First seen · 73 lines · 16 tokens per session scan A f672acd7a445
04-value-routing is an agent published in the GitHub repository assafkip/kipi-system (109 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 676 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.