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/reggiechan74/jobops/findclientnpx skills add reggiechan74/JobOps --skill findclientgit clone --depth 1 https://github.com/reggiechan74/JobOpsWrote 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/reggiechan74/jobops/findclient)<a href="https://agentmods.dev/skills/reggiechan74/jobops/findclient"><img src="https://agentmods.dev/badge/skills/reggiechan74/jobops/findclient.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.1 | $0.00016 | $0.04784 |
| Opus 5 | $0.00008 | $0.02392 |
| Sonnet 5 | $0.00003 | $0.00957 |
| Haiku 4.5 | $0.00002 | $0.00478 |
Grade A, and why
findclient 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 5d 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 — 491 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration
Read .jobops/config.json. If missing, stop with:
JOBOPS NOT CONFIGURED Run /jobops:setup (then /jobops-ic:setup) to initialize your workspace.
Use config.directories.contractor_root for output paths in this skill.
Use config.preferences.default_currency for pricing if applicable.
Arguments
Identifies potential B2B clients through intelligent discovery with 10-point B2B fit scoring and entry point mapping.
Input Options:
<ideal-job-file>: Optional ideal job file from/idealjob--industry=X: Filter by industry--size=startup|mid|enterprise: Company size filter (startup: 1-50, mid: 50-500, enterprise: 500+)--location=X: Geographic filter--limit=N: Max prospects (default: 20, max: 50)
Output: {config.directories.contractor_root}/prospects/[Domain]_[YYYYMMDD].md (Domain = service category/industry, sanitized PascalCase)
Phase 1: Load Prerequisites and Build Targeting Profile
1.1 Check Service Definition Prerequisite
Search for {config.directories.contractor_root}/services/service_definition_*.md. If NOT found, stop with:
SERVICE DEFINITION REQUIRED
Run /defineservices first to create service catalog with ideal client profiles, pricing, and differentiation.
If multiple found, use most recent (latest date in filename).
1.2 Parse Service Definition
Extract from YAML: consultant, generated_on, version
Extract from markdown body:
- Services: name, category, ideal_client (industries, company_size, pain_points, decision_makers)
- Target Market: primary_markets, secondary_markets, avoid_markets, geographic_focus
- Differentiation: competitive_advantages, proof_points
1.3 Parse Command-Line Filters and Optional Ideal Job
Filters:
--industry=X: Narrow to specified industry--size=startup|mid|enterprise: Filter by company size--location=X: Geographic constraint--limit=N: Default 20, max 50
If ideal job file provided ({{ARG1}} ends with .md):
Extract: target industries, company size, location, tech stack, organizational characteristics
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.
- 5d ago First seen · 491 lines · 16 tokens per session scan A f800bd1a36db
findclient is a skill published in the GitHub repository reggiechan74/JobOps (25 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 4,784 once invoked, about $0.0001 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…