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-profilegit 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-profile)<a href="https://agentmods.dev/skills/suxrobgm/jobpilot/upwork-profile"><img src="https://agentmods.dev/badge/skills/suxrobgm/jobpilot/upwork-profile/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-profile"><img src="https://agentmods.dev/badge/skills/suxrobgm/jobpilot/upwork-profile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 26 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.00041 | $0.00994 |
| Opus 5 | $0.00020 | $0.00497 |
| Sonnet 5 | $0.00008 | $0.00199 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
upwork-profile 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsS -H "authorization: Bearer $JOBPILOT_API_TOKEN" -X PUT "$JOBPILOT_API/api/upwork/profile" -H 'content-type: application/json' \ How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upwork Profile Enhancement
Two modes. Default (generate) drafts suggestions for review; apply (argument apply) writes the approved version to the live Upwork profile. Always gate the live write behind the user's approval - never edit the real profile from the generate step.
Setup
Follow ../_shared/setup.md ($JOBPILOT_API is injected by the terminal). Read the resume at primaryResumeSourceAbsolutePath for identity, summary, experience, skills, and projects (the portfolio source). Log in to Upwork via ../_shared/auth.md (resolve via /api/credentials/resolve?domain=upwork.com).
Mode: generate (default)
-
Read the current profile.
browser_navigateto the user's Upwork profile,browser_snapshot(../_shared/browser-tips.md), and capture the currenttitle,overview,hourlyRate, andportfolioprojects. -
Generate suggestions grounded only in resume facts (no fabrication):
- Title - concise, role + top stack (e.g. "Senior React/Node Engineer - SaaS & APIs").
- Overview - lead with the client's outcome, then proof (real projects/metrics from the resume), then a clear CTA. Then invoke the
humanizerskill on it in embedded mode to strip AI tells. - Portfolio - derive entries from resume
projects:{ title, description, url?, skills[] }. Keep existing good ones; add/improve from the resume. - Hourly rate - only suggest if the resume/profile gives a basis; otherwise leave the current value.
-
Save the draft for review:
curl -fsS -H "authorization: Bearer $JOBPILOT_API_TOKEN" -X PUT "$JOBPILOT_API/api/upwork/profile" -H 'content-type: application/json' \ -d "$(jq -n --arg ct "<current title>" --arg co "<current overview>" --arg st "<suggested title>" \ --arg so "<suggested overview>" --argjson cp '<current portfolio json>' --argjson sp '<suggested portfolio json>' \ '{currentTitle:$ct, currentOverview:$co, currentPortfolio:$cp, suggestedTitle:$st, suggestedOverview:$so, suggestedPortfolio:$sp, status:"draft"}')"
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.
- 9d ago First seen · 54 lines · 41 tokens per session scan A b10293e12e70
upwork-profile is a skill published in the GitHub repository suxrobGM/jobpilot (65 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 994 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.
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.
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.