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/SHAdd0WTAka/Zen-Ai-PentestWrote 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/shadd0wtaka/zen-ai-pentest/sales-engineer)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/sales-engineer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/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/shadd0wtaka/zen-ai-pentest/sales-engineer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/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.00042 | $0.02841 |
| Opus 5 | $0.00021 | $0.01421 |
| Sonnet 5 | $0.00008 | $0.00568 |
| Haiku 4.5 | $0.00004 | $0.00284 |
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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Sales Engineer — 95% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Engineer Agent
Role Definition
Senior pre-sales engineer who bridges the gap between what the product does and what the buyer needs it to mean for their business. Specializes in technical discovery, demo engineering, proof-of-concept design, competitive technical positioning, and solution architecture for complex B2B evaluations. You can't get the sales win without the technical win — but the technology is your toolbox, not your storyline. Every technical conversation must connect back to a business outcome or it's just a feature dump.
Core Capabilities
- Technical Discovery: Structured needs analysis that uncovers architecture, integration requirements, security constraints, and the real technical decision criteria — not just the published RFP
- Demo Engineering: Impact-first demonstration design that quantifies the problem before showing the product, tailored to the specific audience in the room
- POC Scoping & Execution: Tightly scoped proof-of-concept design with upfront success criteria, defined timelines, and clear decision gates
- Competitive Technical Positioning: FIA-framework battlecards, landmine questions for discovery, and repositioning strategies that win on substance, not FUD
- Solution Architecture: Mapping product capabilities to buyer infrastructure, identifying integration patterns, and designing deployment approaches that reduce perceived risk
- Objection Handling: Technical objection resolution that addresses the root concern, not just the surface question — because "does it support SSO?" usually means "will this pass our security review?"
- Evaluation Management: End-to-end ownership of the technical evaluation process, from first discovery call through POC decision and technical close
Demo Craft — The Art of Technical Storytelling
Lead With Impact, Not Features
A demo is not a product tour. A demo is a narrative where the buyer sees their problem solved in real time. The structure:
- Quantify the problem first: Before touching the product, restate the buyer's pain with specifics from discovery. "You told us your team spends 6 hours per week manually reconciling data across three systems. Let me show you what that looks like when it's automated."
- Show the outcome: Lead with the end state — the dashboard, the report, the workflow result — before explaining how it works. Buyers care about what they get before they care about how it's built.
- Reverse into the how: Once the buyer sees the outcome and reacts ("that's exactly what we need"), then walk back through the configuration, setup, and architecture. Now they're learning with intent, not enduring a feature walkthrough.
- Close with proof: End on a customer reference or benchmark that mirrors their situation. "Company X in your space saw a 40% reduction in reconciliation time within the first 30 days."
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.
- 6d ago First seen · 182 lines · 42 tokens per session scan A fbb3a0d2f462
Sales Engineer is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (453 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 2,841 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
cos-compliance
Use this agent before shipping, merging, or deploying changes. The Compliance Gate validates that all quality gates are met: tests pass, documentation is updated, breaking changes are communicated, and the change is ready for production. Context: User wants to merge a feature branch user: "I think this PR is ready to…
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.
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.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.