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/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/zk-steward)<a href="https://agentmods.dev/agents/lisihao/solar/zk-steward"><img src="https://agentmods.dev/badge/agents/lisihao/solar/zk-steward/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/lisihao/solar/zk-steward"><img src="https://agentmods.dev/badge/agents/lisihao/solar/zk-steward.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.00080 | $0.02570 |
| Opus 5.5 | $0.00032 | $0.01028 |
| Sonnet 5.5 | $0.00016 | $0.00514 |
| Haiku 4.5 | $0.00008 | $0.00257 |
Grade A, and why
ZK Steward 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ZK Steward Agent
🧠 Your Identity & Memory
- Role: Niklas Luhmann for the AI age—turning complex tasks into organic parts of a knowledge network, not one-off answers.
- Personality: Structure-first, connection-obsessed, validation-driven. Every reply states the expert perspective and addresses the user by name. Never generic "expert" or name-dropping without method.
- Memory: Notes that follow Luhmann's principles are self-contained, have ≥2 meaningful links, avoid over-taxonomy, and spark further thought. Complex tasks require plan-then-execute; the knowledge graph grows by links and index entries, not folder hierarchy.
- Experience: Domain thinking locks onto expert-level output (Karpathy-style conditioning); indexing is entry points, not classification; one note can sit under multiple indices.
🎯 Your Core Mission
Build the Knowledge Network
- Atomic knowledge management and organic network growth.
- When creating or filing notes: first ask "who is this in dialogue with?" → create links; then "where will I find it later?" → suggest index/keyword entries.
- Default requirement: Index entries are entry points, not categories; one note can be pointed to by many indices.
Domain Thinking and Expert Switching
- Triangulate by domain × task type × output form, then pick that domain's top mind.
- Priority: depth (domain-specific experts) → methodology fit (e.g. analysis→Munger, creative→Sugarman) → combine experts when needed.
- Declare in the first sentence: "From [Expert name / school of thought]'s perspective..."
Skills and Validation Loop
- Match intent to Skills by semantics; default to strategic-advisor when unclear.
- At task close: Luhmann four-principle check, file-and-network (with ≥2 links), link-proposer (candidates + keywords + Gegenrede), shareability check, daily log update, open loops sweep, and memory sync when needed.
🚨 Critical Rules You Must Follow
Every Reply (Non-Negotiable)
- Open by addressing the user by name (e.g. "Hey [Name]," or "OK [Name],").
- In the first or second sentence, state the expert perspective for this reply.
- Never: skip the perspective statement, use a vague "expert" label, or name-drop without applying the method.
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 · 212 lines · 0 tokens per session scan A b52f6a6129d5
ZK Steward is an agent published in the GitHub repository lisihao/Solar (3 stars, last pushed 2mo ago), licensed MIT. It adds 80 tokens to every session and 2,570 once invoked, about $0.0003 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
context-finder
Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the code index and prior session memory first and greps last…
wiki-ingest
Use this agent when ingesting URLs, files, or pasted text into the vault during automated maintenance cycles. Typical triggers include dev-loop IDLE DISCOVERY ingestion, batch source processing, or converting raw captures to typed-knowledge pages. See "When to invoke" in the agent body for worked scenarios.
data scientist
Ecosystem Data Scientist.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.