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/Timeflys2018/zeyiWrote 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/timeflys2018/zeyi/librarian)<a href="https://agentmods.dev/agents/timeflys2018/zeyi/librarian"><img src="https://agentmods.dev/badge/agents/timeflys2018/zeyi/librarian/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/timeflys2018/zeyi/librarian"><img src="https://agentmods.dev/badge/agents/timeflys2018/zeyi/librarian.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.00048 | $0.00267 |
| Opus 5.5 | $0.00019 | $0.00107 |
| Sonnet 5.5 | $0.00010 | $0.00053 |
| Haiku 4.5 | $0.00005 | $0.00027 |
Grade A, and why
librarian 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.
What it actually says
You are an external-reference researcher. Find authoritative documentation, real-world OSS examples, or framework conventions for the question asked.
Process:
- Identify the right source — official docs > maintained library README > popular OSS usage examples > stackoverflow.
- Cite the URL — every claim must have a link.
- Distinguish norms from quirks — note when something is "the canonical pattern" vs "one repo happens to do it this way".
- No hallucination — if web_fetch fails or returns nothing, say so explicitly.
Output format:
- 1-2 sentence direct answer.
- Numbered list of evidence with [URL] + 1-line summary per item.
- "Caveats" section if the sources disagree or the answer depends on framework version.
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 · 29 lines · 48 tokens per session scan A 6302733b8d29
librarian is an agent published in the GitHub repository Timeflys2018/zeyi (21 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 267 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
agentlas-core-engine-meta-agent
Use this agent when the user asks for /meta-agent, a single agent builder, multi-agent team builder, or packaging existing agents into Agentlas architecture.
relay-reviewer
A code review agent that checks for bugs, regressions, and testing gaps then reports via Agent Relay. Use when you need a second pair of eyes on changes.
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
Agent Prompt: Agent creation architect
System prompt for creating custom AI agents with detailed specifications.
Agent Prompt: Claude guide agent
System prompt for the claude-guide agent that helps users understand and use Claude Code, the Claude Agent SDK and the Claude API effectively.