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 skills add abullaisi/upwork-skills --skill upwork-job-qualifiergit clone --depth 1 https://github.com/abullaisi/upwork-skillsWrote 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/abullaisi/upwork-skills/upwork-job-qualifier)<a href="https://agentmods.dev/skills/abullaisi/upwork-skills/upwork-job-qualifier"><img src="https://agentmods.dev/badge/skills/abullaisi/upwork-skills/upwork-job-qualifier/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/abullaisi/upwork-skills/upwork-job-qualifier"><img src="https://agentmods.dev/badge/skills/abullaisi/upwork-skills/upwork-job-qualifier.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00146 | $0.01902 |
| Opus 5 | $0.00073 | $0.00951 |
| Sonnet 5 | $0.00029 | $0.00380 |
| Haiku 4.5 | $0.00015 | $0.00190 |
Grade A, and why
upwork-job-qualifier 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 11d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upwork Job Qualifier
Every proposal costs Connects, and the platform's own AI will never tell a freelancer to keep their money: application volume is the platform's revenue. This skill's whole job is the advice that structurally cannot come from inside: when not to apply. Method extracted from a Top Rated Plus freelancer's real invitation ledger and vetting decisions, plus Upwork's own published scam and client-screening guidance.
Inputs
- The job post, pasted in full.
- The "About the client" panel, pasted: payment verified or not, total spent, number of hires, average hourly rate paid, hire rate, member-since date, and the category the job is filed under. This panel decides more verdicts than the job text does. If the user didn't paste it, ask for it before ruling.
- The user's rate and niche, so the math below has a reference point.
Profile shortcut: if a stored profile file exists (upwork-profile.md in the working directory or ~/.claude/), read rate and niche from it and ask only for what's missing or not stated concretely (a rate line that says "ask me" means ask).
Instant skips (any one of these ends the evaluation)
- Any request to pay a fee, buy anything, do unpaid test work, or accept payment outside Upwork.
- Pressure to move communication off-platform before a contract exists.
- Requests for personal information beyond a normal work discussion.
- Payment not verified AND no spend history, on a job promising premium rates.
- A post with no scope, no budget signal, and careless writing throughout. Vague titles with empty descriptions are the fake-post signature.
The client-history cross-check (the highest-value move)
Job titles are marketing. The client's history is data. Run the math:
- Spend per hire: total spent divided by hires. A "specialist" job from a client averaging under $100 per hire is a low-tier gig wearing a nice title.
- Average hourly rate paid vs the user's rate. A client who has paid $8/hr across twelve hires will not pay $80/hr for hire thirteen.
- Category coherence: a premium-sounding title filed under General Virtual Assistance, with data-entry skill tags, is telling the truth in the metadata and lying in the title. Trust the metadata.
- On invitations: the personalized note carries no signal. Invite notes are often templated. The client's posting history is the signal; the flattery is not.
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.
- 11d ago First seen · 95 lines · 146 tokens per session scan A fc310364159a
upwork-job-qualifier is a skill published in the GitHub repository abullaisi/upwork-skills (100 stars, last pushed 1mo ago), licensed MIT. It adds 146 tokens to every session and 1,902 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-08-30.
Other skills, from other repositories
data-charts-tako
Search and visualize the world's data - get charts, insights, and embeddable knowledge cards for finance, economics, demographics, sports, and more.
apollo-lead-finder
Two-phase Apollo.io prospecting: free People Search to discover ICP-matching leads, then selective enrichment to reveal emails/phones (credits per contact). Creates Apollo lists. Deduplicates against existing contacts by LinkedIn URL.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
render-airdrop-carousel
Assemble a viral iOS "AirDrop" notification-carousel video ad (≈6–8s, 9:16) from a brand line plus 6–16 real product photos — a native AirDrop share-sheet card ("Brand would like to share a · Decline / Accept") springs up and its preview window CYCLES through the products, landing on a range/lineup payoff with an…
render-3d-product-showcase
Assemble a premium 3D product-showcase ad from a config — four beat clips (an orbiting hero rotation, a macro push-in, a physics reveal, a typographic close) normalized to the brand-color canvas, hard-concatenated in order, closed on a deterministic Playwright brand end card, and mixed under one instrumental bed at…