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 agentmods add skills/spinningrachel/career-engine/upworknpx skills add spinningrachel/career-engine --skill upworkgit clone --depth 1 https://github.com/spinningrachel/career-engineWrote 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/spinningrachel/career-engine/upwork)<a href="https://agentmods.dev/skills/spinningrachel/career-engine/upwork"><img src="https://agentmods.dev/badge/skills/spinningrachel/career-engine/upwork.svg" alt="Measured on agentmods" 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.00021 | $0.01408 |
| Opus 5 | $0.00010 | $0.00704 |
| Sonnet 5 | $0.00004 | $0.00282 |
| Haiku 4.5 | $0.00002 | $0.00141 |
Grade A, and why
upwork 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 6d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upwork Skill
Platform Overview
Upwork is a contract marketplace where clients post jobs and freelancers submit proposals. Discovery happens two ways: clients find freelancers via profile search, or freelancers find and apply to job posts. Upwork uses a "Connects" credit system for proposals — each application costs 6–16 Connects depending on job budget.
{{USER_FIRST_NAME}}'s use case: positioning as a senior PMM / technical writing consultant. Her buyers are typically Series B+ startups or enterprise teams with real budget and a specific, time-boxed need.
Key Upwork distinction from Fiverr: Upwork buyers are more likely to read proposals carefully and compare. Quality of the proposal outweighs volume of applications. Fiverr is browse-and-click; Upwork is read-and-decide.
MCP Tool Coverage
The Upwork MCP (upwork_search_freelancers) is available for competitive research only — checking market rates, positioning language, and how other senior PMM/TW freelancers present themselves. It does not manage the user's own account. All account actions (proposals, profile edits, contract management) require browser automation via claude-in-chrome.
Profile Copy
Headline
- Max 120 characters
- Most critical surface — it appears in search results and at the top of every proposal
- Format: [specific role] + [specific value] + [context or niche]
- Example structure: "Senior PMM | Technical Writing Strategy for Deep Tech Startups"
- No "guru", "ninja", "rockstar", "expert" (generic); name the specific expertise instead
Overview (Bio)
Structure (4 paragraphs, ~300–500 words total):
- Who you are + what you do — one concrete sentence. The specific intersection of roles and sectors.
- What clients get — the specific outcomes you produce. Named deliverables, not aspirational claims. 2–3 sentences.
- Proof — one or two specific proof points from
02-professional-background.md. Real company names, real contexts. No invented metrics. - How you work — your process and what you need from clients to deliver well. Sets expectations.
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.
- 6d ago First seen · 105 lines · 21 tokens per session scan A 1857172aec3f
upwork is a skill published in the GitHub repository spinningrachel/career-engine (4 stars, last pushed 24d ago), licensed MIT. It adds 21 tokens to every session and 1,408 once invoked, about $0.0001 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…