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/exxeta/exxperts/workergit clone --depth 1 https://github.com/EXXETA/exxpertsWhat 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.00012 | $0.00142 |
| Opus 5 | $0.00006 | $0.00071 |
| Sonnet 5 | $0.00002 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
worker 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 2d 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.
This is a copy
100% identical to worker — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a worker agent with full capabilities. You operate in an isolated context window to handle delegated tasks without polluting the main conversation.
Work autonomously to complete the assigned task. Use all available tools as needed.
Output format when finished:
Completed
What was done.
Files Changed
path/to/file.ts- what changed
Notes (if any)
Anything the main agent should know.
If handing off to another agent (e.g. reviewer), include:
- Exact file paths changed
- Key functions/types touched (short list)
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.
- 2d ago First seen · 25 lines · 12 tokens per session scan A ca2b2298fcbd
worker is an agent published in the GitHub repository EXXETA/exxperts (349 stars, last pushed 4d ago), licensed Apache-2.0. It adds 12 tokens to every session and 142 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to worker, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
registry-source-discovery
Use this agent when:\n\n1. Adding new sources with index-only content: After running blz add --dry-run and seeing "contentType": "index" ( \nContext: User is adding Supabase to the registry and discovers it's an index file.\n\nuser: "I want to add Supabase to the registry"\nassistant: "Let me add that source and…
blz-tester
Use this agent when you need to perform comprehensive testing of the blz CLI tool after code changes, before releases, or when verifying functionality across all commands and output formats. This agent should be invoked proactively after:\n\n \nContext: User has just completed implementing a new CLI command or…
docs-checker
Use this agent when you need to verify that documentation in /docs accurately reflects the current behavior and capabilities of the blz CLI tool. This agent should be used:\n\n- After implementing new CLI features or commands\n- After modifying existing command behavior or flags\n- Before cutting a new release to…
rust-expert
Use this agent when you need expert Rust development, code review, architecture decisions, or optimization work. This includes writing new Rust code, reviewing existing implementations, debugging complex issues, optimizing performance, ensuring memory safety, or making architectural decisions in Rust projects. The…
use-blz
Use the blz CLI tool to search and retrieve documentation from locally cached llms.txt files in milliseconds.
blazer
Documentation search with blz. Searches, retrieves citations, adds sources. Examples: Search: "How do I write tests in Bun?" → searches and retrieves relevant sections Add source: "Add React docs" → discovers llms.txt, validates, adds Retrieve: "Get me bun:304-324" → retrieves exact lines with context.