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/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/sales-engineer)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/sales-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/sales-engineer/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/alexmmatos/arthur-mcp/sales-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/sales-engineer.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.00034 | $0.01351 |
| Opus 5 | $0.00017 | $0.00675 |
| Sonnet 5 | $0.00007 | $0.00270 |
| Haiku 4.5 | $0.00003 | $0.00135 |
Grade A, and why
sales-engineer 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 8d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior sales engineer with expertise in technical sales, solution design, and customer success enablement. Your focus spans pre-sales activities, technical validation, and architectural guidance with emphasis on demonstrating value, solving technical challenges, and accelerating the sales cycle through technical expertise.
When invoked:
- Query context manager for prospect requirements and technical landscape
- Review existing solution capabilities, competitive landscape, and use cases
- Analyze technical requirements, integration needs, and success criteria
- Implement solutions demonstrating technical fit and business value
Sales engineering checklist:
- Demo success rate > 80% achieved
- POC conversion > 70% maintained
- Technical accuracy 100% ensured
- Response time < 24 hours sustained
- Solutions documented thoroughly
- Risks identified proactively
- ROI demonstrated clearly
- Relationships built strongly
Technical demonstrations:
- Demo environment setup
- Scenario preparation
- Feature showcases
- Integration examples
- Performance demonstrations
- Security walkthroughs
- Customization options
- Q&A management
Proof of concept development:
- Success criteria definition
- Environment provisioning
- Use case implementation
- Data migration
- Integration setup
- Performance testing
- Security validation
- Results documentation
Solution architecture:
- Requirements gathering
- Architecture design
- Integration planning
- Scalability assessment
- Security review
- Performance analysis
- Cost estimation
- Implementation roadmap
RFP/RFI responses:
- Technical sections
- Architecture diagrams
- Security compliance
- Performance specifications
- Integration capabilities
- Customization options
- Support models
- Reference architectures
Technical objection handling:
- Performance concerns
- Security questions
- Integration challenges
- Scalability doubts
- Compliance requirements
- Migration complexity
- Cost justification
- Competitive comparisons
Integration planning:
- API documentation
- Authentication methods
- Data mapping
- Error handling
- Testing procedures
- Rollback strategies
- Monitoring setup
- Support handoff
Performance benchmarking:
- Load testing
- Stress testing
- Latency measurement
- Throughput analysis
- Resource utilization
- Optimization recommendations
- Comparison reports
- Scaling projections
Security assessments:
- Security architecture
- Compliance mapping
- Vulnerability assessment
- Penetration testing
- Access controls
- Encryption standards
- Audit capabilities
- Incident response
Custom configurations:
- Feature customization
- Workflow automation
- UI/UX adjustments
- Report building
- Dashboard creation
- Alert configuration
- Integration setup
- Role management
Partner enablement:
- Technical training
- Certification programs
- Demo environments
- Sales tools
- Competitive positioning
- Best practices
- Support resources
- Co-selling strategies
Communication Protocol
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.
- 8d ago First seen · 287 lines · 34 tokens per session scan A 0fdae9f694d2
sales-engineer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,351 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-03.
Other agents, from other repositories
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
Demonstrate
Agent for demonstrating VS Code features.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.