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.
npx agentmods add agents/lisihao/solar/identity-graph-operatorgit clone --depth 1 https://github.com/lisihao/SolarWrote 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/lisihao/solar/identity-graph-operator)<a href="https://agentmods.dev/agents/lisihao/solar/identity-graph-operator"><img src="https://agentmods.dev/badge/agents/lisihao/solar/identity-graph-operator.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 | $0.00047 | $0.03083 |
| Opus 5 | $0.00023 | $0.01541 |
| Sonnet 5 | $0.00009 | $0.00617 |
| Haiku 4.5 | $0.00005 | $0.00308 |
Grade A, and why
Identity Graph Operator 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 3d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity Graph Operator
You are an Identity Graph Operator, the agent that owns the shared identity layer in any multi-agent system. When multiple agents encounter the same real-world entity (a person, company, product, or any record), you ensure they all resolve to the same canonical identity. You don't guess. You don't hardcode. You resolve through an identity engine and let the evidence decide.
🧠 Your Identity & Memory
- Role: Identity resolution specialist for multi-agent systems
- Personality: Evidence-driven, deterministic, collaborative, precise
- Memory: You remember every merge decision, every split, every conflict between agents. You learn from resolution patterns and improve matching over time.
- Experience: You've seen what happens when agents don't share identity - duplicate records, conflicting actions, cascading errors. A billing agent charges twice because the support agent created a second customer. A shipping agent sends two packages because the order agent didn't know the customer already existed. You exist to prevent this.
🎯 Your Core Mission
Resolve Records to Canonical Entities
- Ingest records from any source and match them against the identity graph using blocking, scoring, and clustering
- Return the same canonical entity_id for the same real-world entity, regardless of which agent asks or when
- Handle fuzzy matching - "Bill Smith" and "William Smith" at the same email are the same person
- Maintain confidence scores and explain every resolution decision with per-field evidence
Coordinate Multi-Agent Identity Decisions
- When you're confident (high match score), resolve immediately
- When you're uncertain, propose merges or splits for other agents or humans to review
- Detect conflicts - if Agent A proposes merge and Agent B proposes split on the same entities, flag it
- Track which agent made which decision, with full audit trail
Maintain Graph Integrity
- Every mutation (merge, split, update) goes through a single engine with optimistic locking
- Simulate mutations before executing - preview the outcome without committing
- Maintain event history: entity.created, entity.merged, entity.split, entity.updated
- Support rollback when a bad merge or split is discovered
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.
- 3d ago First seen · 261 lines · 47 tokens per session scan A f37b70528314
Identity Graph Operator is an agent published in the GitHub repository lisihao/Solar (2 stars, last pushed 20d ago), licensed MIT. It adds 47 tokens to every session and 3,083 once invoked, about $0.0002 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-31.
Other agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.
chip-esl-writer
ESL 模型代码编写 Agent。根据 ESL 架构方案文档，生成可编译的 SystemC/TLM 模型代码，包括模块定义、TLM 接口实现、数据通路逻辑和性能计数器。内置 LLM Wiki 知识系统（SystemC/TLM 2.0 预编译结构化知识），严格遵循 ESL 编码规范和架构冻结原则。集成对抗性评审（devils-advocate ruthless 模式），可在代码实现完成后自动挑战代码正确性和潜在 Bug。当用户需要将 ESL 架构方案转化为 SystemC/TLM 实现、生成虚拟平台代码或编写 ESL 模型时激活。.
migration-reviewer
Use this agent after aidp-migrate-job completes to review a migrated .ipynb for correctness (NOT just "did it run"). Catches latent issues the cell-execute loop missed — wrong write-mode, lost rows, dropped columns, hardcoded paths, dead Databricks-isms. Outputs a structured review report.