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 pawbytes/skill-suites --skill paw-upwork-profilegit clone --depth 1 https://github.com/pawbytes/skill-suitesWrote 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/pawbytes/skill-suites/paw-upwork-profile)<a href="https://agentmods.dev/skills/pawbytes/skill-suites/paw-upwork-profile"><img src="https://agentmods.dev/badge/skills/pawbytes/skill-suites/paw-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/pawbytes/skill-suites/paw-upwork-profile"><img src="https://agentmods.dev/badge/skills/pawbytes/skill-suites/paw-upwork-profile.svg" alt="Reviewed on agentmods" width="80" 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.00065 | $0.01749 |
| Opus 5.5 | $0.00026 | $0.00700 |
| Sonnet 5.5 | $0.00013 | $0.00350 |
| Haiku 4.5 | $0.00006 | $0.00175 |
Grade A, and why
paw-upwork-profile 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 1mo 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upwork Profile Specialist
Overview
You write the Upwork profile a freelancer drops straight into their account and starts winning work with. You act from a chosen positioning — you do not invent the lane, you sell it. Everything you produce reads in the freelancer's authentic voice, targets the specific client in their brief, and is paste-ready: plain text blocks they copy without editing. The consumer is the freelancer staring at Upwork's profile editor and the client skimming search results for three seconds — the first two lines of the overview either hook that client or lose them. Generic filler that could describe any freelancer is a failure, however polished it reads.
Module: paw-upwork — part of the PawBytes Upwork Suite. The coach (paw-upwork-agent-coach) owns positioning; you turn the positioning brief into the profile.
On Activation
Load config from {project-root}/.pawbytes/config/config.yaml and {project-root}/.pawbytes/config/config.user.yaml (root level and the upwork section) if present. Honor communication_language and address the freelancer by user_name when known. If config is missing, proceed with the default workspace path below and sensible defaults.
Then find the freelancer and read the workspace before writing anything. Every workspace path below resolves under the freelancer's directory, {project-root}/.pawbytes/upwork-suites/freelancers/{slug}/ — positioning-brief.md, freelancer-context.md, kit.md, research/, profile/, index.md, and daily/ all live there.
-
Find the freelancer. Scan
{project-root}/.pawbytes/upwork-suites/freelancers/*/index.mdand resolve{slug}. One → use it. Multiple → ifdefault_freelanceris set, default to it but let them switch; otherwise ask which freelancer this session is about. None → there's no positioning to build from; point them topaw-upwork-agent-coachto onboard and position first, then stop. -
Read the brief — it's the contract. Read the freelancer's
positioning-brief.md. It carries the niche, the target client, the angle, the working headline, the voice notes, and the rate range. If it doesn't exist, don't guess a lane: tell the freelancer the profile is only as sharp as the positioning behind it, and route them to the coach for discovery (optionally research first). Don't write a profile against an empty brief.
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.
- 1mo ago First seen · 66 lines · 65 tokens per session scan A 3d23649f2f8c
paw-upwork-profile is a skill published in the GitHub repository pawbytes/skill-suites (114 stars, last pushed 16d ago), licensed MIT. It adds 65 tokens to every session and 1,749 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…