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/phone-validatornpx skills add DataSift-Ty-Personal/SiftStack --skill phone-validatorgit clone --depth 1 https://github.com/DataSift-Ty-Personal/SiftStackWhat 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.00166 | $0.05561 |
| Opus 5 | $0.00083 | $0.02780 |
| Sonnet 5 | $0.00033 | $0.01112 |
| Haiku 4.5 | $0.00017 | $0.00556 |
Grade A, and why
phone-validator 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 3d 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 — 528 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phone Validator & Tagger
Score phone numbers using Trestle's phone_intel API and produce DataSift/REISift-ready CSVs with phone tags for prioritized dialing.
Execution Mode Detection
Before starting, detect the execution environment for the DataSift upload step:
Check 1: Does scripts/upload_phone_tags.py exist in this skill's directory?
Check 2: Is Playwright available? Run: python -c "from playwright.sync_api import sync_playwright; print('OK')"
Check 3: Are credentials set? Check for DATASIFT_EMAIL and DATASIFT_PASSWORD in .env or environment.
Automated Upload Mode (Claude Code CLI — all 3 checks pass)
After running scripts/validate_phones.py to generate the phone tags CSV, upload directly:
# Upload validated phone tags to DataSift
python scripts/upload_phone_tags.py --csv phone_tags_for_datasift.csv
# Headless mode (no visible browser)
python scripts/upload_phone_tags.py --csv phone_tags_for_datasift.csv --headless
The script handles login, navigating to Upload File -> Update Data -> "Tag phones by phone number", file upload, column mapping, and completion automatically.
Manual Upload Mode (Co-Work or no Playwright — any check fails)
After generating the phone tags CSV, follow the manual DataSift upload instructions in the "Upload to DataSift" section below.
What This Skill Does
This skill takes a CSV of phone numbers — typically a DataSift "Phone Enrichment" export
with Phone 1 through Phone 30 columns — runs each unique number through Trestle's Phone
Validation API to get an activity score and line type, then assigns a phone tag tier based
on configurable score thresholds. The output is a two-column CSV (Phone Number, Phone Tag)
formatted for direct upload to DataSift/REISift using their "Update Data → Tag phones by
phone number" workflow.
The Pipeline
Input CSV (DataSift Phone Enrichment export or any CSV with phone columns)
→ Parse all phone columns (Phone 1 through Phone 30)
→ Deduplicate across all columns and rows (saves API cost)
→ ESTIMATE COST & GET USER CONFIRMATION
→ Trestle phone_intel API (activity_score + line_type)
→ Score-based tier assignment (Dial First, Dial Second, Dial Third, Dial Fourth, Drop)
→ DataSift-ready CSV (Phone Number | Phone Tag)
→ Upload to DataSift via "Update Data → Tag phones by phone number"
What ships with it
5 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.
- 3d ago First seen · 528 lines · 166 tokens per session scan A ada1ef02b3c5
phone-validator is a skill published in the GitHub repository DataSift-Ty-Personal/SiftStack (21 stars, last pushed 5d ago), licensed MIT. It adds 166 tokens to every session and 5,561 once invoked, about $0.0008 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…