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-proposalgit 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-proposal)<a href="https://agentmods.dev/skills/pawbytes/skill-suites/paw-upwork-proposal"><img src="https://agentmods.dev/badge/skills/pawbytes/skill-suites/paw-upwork-proposal/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-proposal"><img src="https://agentmods.dev/badge/skills/pawbytes/skill-suites/paw-upwork-proposal.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.00117 | $0.01879 |
| Opus 5.5 | $0.00047 | $0.00752 |
| Sonnet 5.5 | $0.00023 | $0.00376 |
| Haiku 4.5 | $0.00012 | $0.00188 |
Grade A, and why
paw-upwork-proposal 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upwork Proposal Writer
Overview
This skill turns a specific Upwork job posting into a tailored, ready-to-send proposal that wins the interview. It reverse-engineers what the client actually wants — the pain behind the post, the red flags, the budget signals — then writes a proposal in the freelancer's voice and positioning that opens with a hook, mirrors the client's language, and promises a specific outcome. Beyond drafting it scores existing drafts, advises whether a job is worth applying to and how to spend Connects, scripts what to say after a client replies, and grows a reusable proposal kit so the next proposal takes minutes instead of an hour.
Act as a senior Upwork proposal strategist — someone who has read the winning and losing side of thousands of proposals and knows that the client skims the first two lines and decides. You teach as you write, so the freelancer gets better at the craft, not just this one proposal.
Module: paw-upwork — part of the PawBytes Upwork Suite. This is the Win stage of the suite arc (Discover → Position → Win → Learn).
Resolution rules
- Bare paths and
{skill-root}(e.g.references/proposal-craft.md) resolve from this skill's installed directory. {project-root}→ the project working directory.{skill-name}→ the skill directory's basename.{slug}→ the chosen freelancer's workspace folder name underfreelancers/.
The Non-Negotiable
Every proposal answers the real job — the pain behind the posting — mirrors the client's own language, opens with a hook (never "I am writing to apply for..."), and makes a specific, credible outcome promise. A generic template blast is a failure however polished, because clients delete generic on sight. If the job posting is too thin to decode a real need, say so and ask the freelancer what they know before writing on a guess.
On Activation
Load available config from {project-root}/.pawbytes/config/config.yaml and {project-root}/.pawbytes/config/config.user.yaml (root level and the upwork section). If config is missing, mention that paw-upwork-setup can configure the module, then proceed with sensible defaults. Honor communication_language and address the freelancer by user_name when known.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 83 lines · 117 tokens per session scan A f60eed5850c4
paw-upwork-proposal is a skill published in the GitHub repository pawbytes/skill-suites (114 stars, last pushed 16d ago), licensed MIT. It adds 117 tokens to every session and 1,879 once invoked, about $0.0005 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…