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 skills/datasift-ty-personal/siftstack/lead-manager-coachnpx skills add DataSift-Ty-Personal/SiftStack --skill lead-manager-coachgit clone --depth 1 https://github.com/DataSift-Ty-Personal/SiftStackWrote 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/skills/datasift-ty-personal/siftstack/lead-manager-coach)<a href="https://agentmods.dev/skills/datasift-ty-personal/siftstack/lead-manager-coach"><img src="https://agentmods.dev/badge/skills/datasift-ty-personal/siftstack/lead-manager-coach.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.00099 | $0.00700 |
| Opus 5 | $0.00049 | $0.00350 |
| Sonnet 5 | $0.00020 | $0.00140 |
| Haiku 4.5 | $0.00010 | $0.00070 |
Grade A, and why
lead-manager-coach 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 4d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead Manager Coach
Grades lead-management calls (follow-ups, qualification, nurture touches,
revivals) against the DataSift Lead Manager playbook. Same pipeline as the
cold-call-coach skill; this skill applies the lead-management rubric to calls
the triage step classified as lead_management.
Requirements, setup, and costs
Identical to the cold-call-coach skill (same scripts, same session, same .env):
python scripts/smrtphone_login.py once, OPENROUTER_API_KEY in .env,
optional roster.json. Transcription costs about $0.002 per audio minute.
Pipeline
python scripts/pull_calls.py --min-seconds 60 --days 7
python scripts/transcribe.py
Then take the lead_management group with worth_grading: true from
output/call_coaching/review_queue.json. Transcripts live at
output/call_coaching/transcripts/{call_id}.md and include a DELIVERY SUMMARY
with real audio observations plus a label check line.
Grading procedure
- Read
references/rubric.mdfully (gate, short-call rule, auto-fails, 5 categories weighted 10/30/20/20/20, anchors, templates, the required SCORES JSON footer). - Read the whole transcript once; verify AGENT/SELLER labels by content; route full vs short (short = a decline inside ~30 seconds; doubt resolves to full).
- Score criterion by criterion against the 0/3/5 anchors (quote required),
write one report per call to
output/call_coaching/reports/lead_management/{call_id}_{caller}.mdwith the CRITERION SCORES table and SCORES JSON footer, then a per-caller scorecard. - Export:
python scripts/export_excel.py --dir output/call_coaching/reports/lead_management
Grading quality protocol (mandatory verify pass)
Same as cold-call-coach: verbatim quotes only, evidence per criterion, N/A discipline with listed redistribution, math that foots exactly with a matching JSON footer, call-audible content only, and full vs short calls never ranked in one column.
Failure modes
Session expired: re-run python scripts/smrtphone_login.py. Key error: set
OPENROUTER_API_KEY in .env. A call misclassified between cold_call and
lead_management: trust your read of the transcript, note the reroute.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 63 lines · 99 tokens per session scan A 0fcb65130a3c
lead-manager-coach is a skill published in the GitHub repository DataSift-Ty-Personal/SiftStack (21 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 700 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…