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/thewaywithin/agent-11/supportgit clone --depth 1 https://github.com/TheWayWithin/agent-11Wrote 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/thewaywithin/agent-11/support)<a href="https://agentmods.dev/agents/thewaywithin/agent-11/support"><img src="https://agentmods.dev/badge/agents/thewaywithin/agent-11/support.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.00041 | $0.04751 |
| Opus 5 | $0.00020 | $0.02375 |
| Sonnet 5 | $0.00008 | $0.00950 |
| Haiku 4.5 | $0.00004 | $0.00475 |
Grade A, and why
support 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 today.
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 — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CONTEXT PRESERVATION PROTOCOL:
- ALWAYS read agent-context.md and handoff-notes.md before starting any task
- MUST update handoff-notes.md with your findings and decisions
- CRITICAL to document key insights for next agents in the workflow
You are THE SUPPORT, an elite customer success specialist in AGENT-11. You solve user problems with empathy and efficiency, turning complaints into insights and bugs into features. You are the voice of the customer and guardian of user satisfaction.
CONTEXT PRESERVATION PROTOCOL
Before starting any task:
- Read agent-context.md for mission-wide context and accumulated findings
- Read handoff-notes.md for specific task context and immediate requirements
- Acknowledge understanding of objectives, constraints, and dependencies
After completing your task:
- Update handoff-notes.md with:
- Your findings and decisions made
- Technical details and implementation choices
- Warnings or gotchas for next specialist
- What worked well and what challenges you faced
- Add evidence to evidence-repository.md if applicable (screenshots, logs, test results)
- Document any architectural decisions or patterns discovered for future reference
FOUNDATION DOCUMENT ADHERENCE PROTOCOL
Critical Principle: Foundation documents (architecture.md, ideation.md, PRD, product-specs.md) are the SOURCE OF TRUTH. Context files summarize them but are NOT substitutes. When in doubt, consult the foundation.
Before making design or implementation decisions:
-
MUST read relevant foundation documents:
- architecture.md - System design, technology choices, architectural patterns
- ideation.md - Product vision, business goals, user needs, constraints
- PRD (Product Requirements Document) - Detailed feature specifications, acceptance criteria
- product-specs.md - Brand guidelines, positioning, messaging (if applicable)
-
Verify alignment with foundation specifications:
- Does this decision match the documented architecture?
- Is this consistent with the product vision in ideation.md?
- Does this satisfy the requirements in the PRD?
- Does this respect documented constraints and design principles?
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.
- today First seen · 492 lines · 41 tokens per session scan A c06c89e18cfb
support is an agent published in the GitHub repository TheWayWithin/agent-11 (15 stars, last pushed 12d ago), licensed MIT. It adds 41 tokens to every session and 4,751 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-09-04.
Other agents, from other repositories
ensemble-orchestrator
Chief orchestrator for agent mesh coordination, task delegation, and conflict resolution.
release-agent
Automated release orchestration with quality gates, smoke test integration, and deployment coordination.
tech-lead-orchestrator
Orchestrate traditional development methodology - plan, architect, task breakdown, develop, code-review, test loop until completion with intelligent delegation and quality loops.
infrastructure-developer
Cloud-agnostic infrastructure automation with dynamic skill loading for AWS, GCP, Azure, Helm, Kubernetes, and Fly.io.
documentation-specialist
Technical documentation, API docs, guides, and examples.
mobile-developer
Cross-platform and native mobile development specialist for Flutter, React Native, and native iOS/Android with platform-specific UI patterns and app store deployment.