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 suxrobGM/jobpilot --skill upwork-searchgit clone --depth 1 https://github.com/suxrobGM/jobpilotWrote 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/suxrobgm/jobpilot/upwork-search)<a href="https://agentmods.dev/skills/suxrobgm/jobpilot/upwork-search"><img src="https://agentmods.dev/badge/skills/suxrobgm/jobpilot/upwork-search/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/suxrobgm/jobpilot/upwork-search"><img src="https://agentmods.dev/badge/skills/suxrobgm/jobpilot/upwork-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 49 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 71 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 85 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 96 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00040 | $0.02373 |
| Opus 5 | $0.00020 | $0.01187 |
| Sonnet 5 | $0.00008 | $0.00475 |
| Haiku 4.5 | $0.00004 | $0.00237 |
Grade A, and why
upwork-search scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
4. Resolve the board: `curl -fsS -H "authorization: Bearer $JOBPILOT_API_TOKEN" "$JOBPILOT_API/api/job-boards" | jq '.[] | select(.domain=="upwork.com")'`. How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upwork Job Search & Recommend
Find Upwork jobs the user can win - qualify on fit and client quality, drop the junk, and save
the keepers to the campaign for review. Recommend only: never submit a proposal here. The user
drafts a proposal (the upwork-proposal skill, launched per job from the campaign page) and
sends it with the upwork-submit skill.
Setup
- Follow
../_shared/setup.md($JOBPILOT_APIis injected by the terminal). - Follow
../_shared/upwork-mcp.md: confirm the Upwork tools are connected and resolveORG_UIDonce. Not connected → stop with the message that doc gives. There is no browser fallback. - Parse and strip the flags; the rest is the free-text query.
--board upwork.com- required.--max-jobs <N>- cap on results to evaluate. Absent = 30. Pages are 10 at most, so the cap sets how many cursor round trips you make.--campaign <id>- campaign to save to. The UI passes it; if absent, match the latestsource:"search",status:"in_progress"campaign on the query, else create one (asource:"search"create requiresconfig.resumeId- default to the profile'sprimaryResumeId).
- Resolve the board:
curl -fsS -H "authorization: Bearer $JOBPILOT_API_TOKEN" "$JOBPILOT_API/api/job-boards" | jq '.[] | select(.domain=="upwork.com")'. No row → abort: "Upwork is not configured. Add it on /boards." If a--campaignwas given, first command it tofailedwithPOST /api/campaigns/<id>/status {"status":"failed"}.
Phase 1: Parse Query
Extract the role and skills, and the preferences the search can filter on directly: hourly vs fixed, budget or rate floor, client location, weekly hours, project length. If vague, ask before searching.
Push every preference you extracted into the search parameters rather than filtering afterwards.
Always set verified_payment_only: true and proposals_max: 49 - both are hard skips downstream,
so paying for those rows wastes a page.
Phase 2: Search Upwork
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.
- today Changed · +54 lines 28b20efe7045
- 9d ago First seen · 110 lines · 40 tokens per session scan A e0da13995e4f
upwork-search is a skill published in the GitHub repository suxrobGM/jobpilot (66 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 2,373 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
security
Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.