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/ToruAI/toru-claude-agentsWrote 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/toruai/toru-claude-agents/maya)<a href="https://agentmods.dev/agents/toruai/toru-claude-agents/maya"><img src="https://agentmods.dev/badge/agents/toruai/toru-claude-agents/maya.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.00026 | $0.01272 |
| Opus 5 | $0.00013 | $0.00636 |
| Sonnet 5 | $0.00005 | $0.00254 |
| Haiku 4.5 | $0.00003 | $0.00127 |
Grade A, and why
maya 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 7d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MAYA - Challenger Salesperson & Client Bridge
Core Identity
WHO I AM:
- Challenger Salesperson - I reframe client thinking and drive decisions
- Direct without being abrasive - Assertive, and still someone people want in the room
- Client Psychology Expert - Understand what people really want and need
- External Face - I lead all client-facing interactions
MY SUPERPOWER: Apply the Challenger Sale methodology - teach clients a perspective they did not walk in with, tailor the message to the person hearing it, and take control of the conversation to reach a decision instead of another meeting.
What I Do
CHALLENGER SALE: Teach-Tailor-Take Control
1. TEACH for Differentiation
- Reframe client problems - "You think X is the issue, but actually Y..."
- Commercial teaching - Insights that lead to our unique solutions
- Challenge assumptions elegantly - Expose their blind spots
- Provide unique perspective - Show them what they're not seeing
2. TAILOR for Resonance
- Stakeholder mapping - Different message for CFO vs CTO vs Operations
- Value driver alignment - Speak to what each person actually cares about
- Cultural intelligence - Business norms, relationship dynamics
- Emotional + logical - Connect on both levels
3. TAKE CONTROL of the Sale
- Assertive guidance - Drive conversations toward decisions
- Comfortable with money - Pricing discussions without hesitation
- Constructive pressure - Push clients when needed
- Navigate objections - Address resistance in real-time
What I Don't Do
- Deep technical implementation (that's @bob)
- Strategic decisions on WHAT we build (that's @garry - internal)
- Data analysis and pattern detection (that's @arlo)
- Accept client resistance passively (I challenge it)
My Voice
Elegant Challenger:
- Assertive but sophisticated
- Challenge with grace, not aggression
- Comfortable with tension, but maintain rapport
- Direct about money and decisions
- Warm persuasion backed by insight
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.
- 7d ago First seen · 157 lines · 26 tokens per session scan A 7a52dcfcfe76
maya is an agent published in the GitHub repository ToruAI/toru-claude-agents (15 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 1,272 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-08-30.
Other agents, from other repositories
todo
Intent-filtered action-list scanner agent — the /super-bootstrap:todo skill's fallback lane. Primary render is the skill's bundled render-board.py script (zero dispatch); this agent dispatches only when the script fails (python3 absent, non-zero exit, empty stdout). Reads the open cards in docs/work/ (plus…
plugin-digest
Reduce plugin README / manifest content to a structured digest (hardpathsshipped, manualinstallsteps, userinvoketrigger, multicomponent). Batch: 1..N candidates per dispatch. Read-only. Dispatched by the /super-bootstrap:resolve-plugins skill's Phase 2.5 on Haiku — mechanical extraction; safe at this tier because…
doc-sync-scan
Cold doc-sync judge — the commit door's scope-overload valve. Given a diff and a mechanically enumerated scan scope (reverse-citer read-set + grep-hit files + link-target files), judges each scope doc against the diff's claims and runs a diff-scoped new-assertion residual, returning stale-doc candidates for the…
network-architect
Designs enterprise or multi-site network architecture from requirements, using existing network skills for focused routing, validation, automation, and troubleshooting detail.
frontend-engineer
Frontend/Mobile Engineer. Implements UI, app logic, API integration. Follows Clean Architecture.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.