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/greglas75/zuvo/leadsnpx skills add greglas75/zuvo --skill leadsgit clone --depth 1 https://github.com/greglas75/zuvoWrote 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/greglas75/zuvo/leads)<a href="https://agentmods.dev/skills/greglas75/zuvo/leads"><img src="https://agentmods.dev/badge/skills/greglas75/zuvo/leads.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.00178 | $0.04993 |
| Opus 5 | $0.00089 | $0.02497 |
| Sonnet 5 | $0.00036 | $0.00999 |
| Haiku 4.5 | $0.00018 | $0.00499 |
Grade E, and why
leads scanned grade E with 4 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
clear message (`chmod 600 ~/.zuvo/config.toml` or set the override env var for local Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
`docs/../../etc/shadow`). Reject with exit 2 if the resolved path is outside allowed Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$OUTDIR/.lock" && retry_acquisition Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| GitHub API | `curl -sS -o /dev/null -w '%{http_code}' https://api.github.com/rate_limit` | optional | How it starts
The opening of the file, as written. The whole thing — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.
zuvo:leads
Free-tier B2B contact discovery orchestrator. Runs a 7-phase pipeline with interactive checkpoints, parallel-agent dispatch, graceful degradation when tools are missing, and atomic output writes.
Argument Parsing
| Flag | Type | Default | Purpose |
|---|---|---|---|
--industry "<term>" |
string | — | discovery-mode filter |
--geo "<country|city>" |
string | — | ISO 3166-1 code or city name |
--role "<title>" |
string | — | target role |
--seniority <level> |
enum | any | c-level,vp,director,manager,ic |
--size-band <band> |
enum | any | 1-10/11-50/.../5001+ |
--max-results N |
int | 50 | hard cap on contacts |
--max-companies N |
int | derived | default: ceil(max-results/2) |
--domains <file> |
path | — | triggers enrichment mode |
--dedup-against <file> |
path | — | suppress matching records |
--gdpr-strict |
bool | false | enable GDPR restrictions |
--keep-phones |
bool | false | only with --gdpr-strict; retain all phones |
--output <slug> |
string | derived | filename stem |
--resume |
bool | false | continue from checkpoint |
--no-interactive |
bool | false | auto-accept checkpoints, emit [AUTO-CHECKPOINT] |
--dry-run |
bool | false | plan only, no network calls |
Env vars (all optional): ZUVO_HUNTER_KEY, ZUVO_APOLLO_KEY, ZUVO_GITHUB_TOKEN,
ZUVO_LEADS_OUTPUT_DIR, ZUVO_LEADS_DISABLED, ZUVO_SMTP_PROBE_CMD,
ZUVO_LEADS_ALLOW_INSECURE_CONFIG. API keys MUST come from env/config only — NEVER
from CLI flags.
Mandatory File Loading
CORE FILES LOADED:
1. ../../shared/includes/env-compat.md -- READ/MISSING
2. ../../shared/includes/live-probe-protocol.md -- READ/MISSING
3. ../../shared/includes/lead-output-schema.md -- READ/MISSING
4. ../../shared/includes/lead-source-registry.md -- READ/MISSING
5. ../../shared/includes/knowledge-prime.md -- READ/MISSING
6. ../../shared/includes/knowledge-curate.md -- DEFERRED (completion)
7. ../../shared/includes/run-logger.md -- DEFERRED (completion)
8. ../../shared/includes/retrospective.md -- DEFERRED (completion)
9. ../../shared/includes/adversarial-loop-docs.md -- OPTIONAL
What ships with it
3 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 · 395 lines · 178 tokens per session scan E 0f531d11b4c7
leads is a skill published in the GitHub repository greglas75/zuvo (6 stars, last pushed today), licensed MIT. It adds 178 tokens to every session and 4,993 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it E with 4 findings (asks for root, reaches for credential files, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
debt-ops-init
Write or refresh a "Tech debt operations" section in the project's AGENTS.md so the team shares one source of truth for debt-ops disciplines. Run ONLY when the user explicitly asks to set up, install, or initialize debt-ops disciplines — never auto-invoke. Idempotent; only the managed section changes, other sections…
init
Write or refresh the ## Tech debt operations section in CLAUDE.md so a team shares one source of truth for debt-ops disciplines and cached quality commands. Idempotent. Only the managed section changes; other sections are untouched. Invoked explicitly via /debt-ops:init (solo users get the same content from the…
review
Audit the debt registry, rank survivors by churn × Fowler quadrant, surface a top-N list, then walk paydown on user follow-up. Use when the user asks to review debt, see what to pay down, work through entries, or invokes /debt-ops:review. Stale entries drop with drop A,B,C.
debt-ops-metrics
Print a debt-ops health summary from the metrics log, covering registration rate, feedback action rate, ADR creation, and AI-authored share. Use when the user asks for "debt-ops metrics", "debt health", "registry stats", or a tech-debt health summary. Read-only, never writes the log.
add
Register a deferred decision in the debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you defer…
metrics
Print a debt-ops health summary from the metrics log, covering registration rate, hook feedback action rate, ADR creation, and AI-authored share. Use when the user asks for "debt-ops metrics", "debt health", "registry stats", or invokes /debt-ops:metrics. Read-only, never writes the log.