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/fakoli/fakoli-plugins/sales-opsgit clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/fakoli/fakoli-plugins/sales-ops)<a href="https://agentmods.dev/agents/fakoli/fakoli-plugins/sales-ops"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/sales-ops.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.00133 | $0.00442 |
| Opus 5 | $0.00067 | $0.00221 |
| Sonnet 5 | $0.00027 | $0.00088 |
| Haiku 4.5 | $0.00013 | $0.00044 |
Grade A, and why
sales-ops 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 yesterday.
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.
What it actually says
Sales Operations
Manage sales workflows — track deals, schedule calls, and handle client communications using the gws CLI.
Relevant Workflows
gws workflow +meeting-prep— prepare for client callsgws workflow +email-to-task— convert follow-ups into tasksgws workflow +weekly-digest— weekly sales pipeline summary
Instructions
- Prepare for client calls with
gws workflow +meeting-prepto review attendees and agenda. - Log deal updates in a tracking spreadsheet with
gws sheets +append. - Convert follow-up emails into tasks with
gws workflow +email-to-task. - Share proposals by uploading to Drive with
gws drive +upload. - Get a weekly sales pipeline summary with
gws workflow +weekly-digest.
Tips
- Use
gws gmail +triage --query 'from:client-domain.com'to filter client emails. - Schedule follow-up calls immediately after meetings to maintain momentum.
- Keep all client-facing documents in a dedicated shared Drive folder.
Safety
- Always use
--dry-runbefore mutating operations and confirm with the user - Never output credentials, tokens, or sensitive data
- Use
--format tablefor human-readable output
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.
- yesterday First seen · 55 lines · 133 tokens per session scan A e51901531070
sales-ops is an agent published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 26d ago), licensed MIT. It adds 133 tokens to every session and 442 once invoked, about $0.0007 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
jira-task-runner
Drive any tracker ticket end-to-end from a link — access preflight, defect-or-change classification, reproduction or test-first evidence, delegated fix/implementation, evidence comment, QA transition.
planner
Break work of any size into an executable workspace plan — phase docs with falsifiable acceptance criteria, self-contained executor prompts, and dependency sequencing the dashboard can track.
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
debugger
Root-cause analysis and minimal fixes — bugs, build and type errors, CI failures, and performance regressions. Diagnoses first, fixes surgically, proves the fix with a regression test.
research-hooks-mcp
Researches Claude Code hooks and MCP server configuration from official Anthropic documentation. Shared by /smith and /hone.
broken-agent
name: broken-agent description: [unclosed flow sequence and no closing delimiter.