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 abullaisi/upwork-skills --skill upwork-invitation-respondergit clone --depth 1 https://github.com/abullaisi/upwork-skillsWrote 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/abullaisi/upwork-skills/upwork-invitation-responder)<a href="https://agentmods.dev/skills/abullaisi/upwork-skills/upwork-invitation-responder"><img src="https://agentmods.dev/badge/skills/abullaisi/upwork-skills/upwork-invitation-responder/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/abullaisi/upwork-skills/upwork-invitation-responder"><img src="https://agentmods.dev/badge/skills/abullaisi/upwork-skills/upwork-invitation-responder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Anti-Refusal · line 18 Skill instructs the agent to never refuse or to always comply. Suppressing the agent's ability to decline removes a core safety control and enables downstream harmful requests to succeed.Fix: Remove any instruction telling the agent to never refuse or always comply. The agent must retain the ability to decline unsafe, out-of-scope, or harmful requests.
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.01261 |
| Opus 5.5 | $0.00047 | $0.00504 |
| Sonnet 5.5 | $0.00023 | $0.00252 |
| Haiku 4.5 | $0.00012 | $0.00126 |
Grade A, and why
upwork-invitation-responder 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 2mo 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upwork Invitation Responder
Invitations are not job applications. The client already handpicked this freelancer's profile and is asking for a proposal. That changes the reply's job: the credibility argument is half-won, speed and clarity do the rest. Method extracted from a Top Rated Plus freelancer's real invitation threads plus Upwork's published guidance.
Inputs
- The invitation (job post or invite message), pasted.
- The user's decision: accept, decline, or unsure. If unsure, run the triage below first.
- For accepts: one portfolio link matched to the job. For decline-with-referral: the referral's name and whether the user has already told them.
Profile shortcut: if a stored profile file exists (upwork-profile.md in the working directory or ~/.claude/), read identity, niche, and links from it and ask only for what's missing or not stated concretely (a rate line that says "ask me" means ask).
Rule zero: always respond, same day
Silence is the worst possible reply, and it is not private: the job's activity panel shows clients a counted "Unanswered invites" stat next to "Invites sent." An ignored invitation is a visible number on the client's screen. Every invitation gets an answer, even a two-line decline. If invitations arrive faster than the freelancer can handle, the fix is the profile availability setting ("Not Available"), never silence.
Triage (when the user is unsure)
Three questions, thirty seconds:
- Would you do this work at your current rate? If the answer needs a rate raise to become yes, it's a decline.
- Does your portfolio already prove this niche? If proving fit requires explaining, the client picked the wrong person; decline or refer.
- Do you have capacity inside their timeline? Busy-but-interested is still a decline (or a referral), never a slow maybe.
Two or three yeses: accept. Otherwise pick the decline move that fits.
Question 1 is a hard gate. If getting to yes needs a rate raise, it's a decline no matter how the other two land.
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.
- 2mo ago First seen · 69 lines · 117 tokens per session scan A 617b7af34585
upwork-invitation-responder is a skill published in the GitHub repository abullaisi/upwork-skills (125 stars, last pushed 7d ago), licensed MIT. It adds 117 tokens to every session and 1,261 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-08-30.
upwork-invitation-responder compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| upwork-invitation-responderabullaisi/upwork-skills | Skill | 125 | 7d ago | MIT | A | 117 | Claude Code, Codex |
| x-tweet-by-conversationbrowser-act/skills | Skill | 6.3k | 2d ago | MIT | A | 218 | Claude Code, Codex |
| oma-scholarfirst-fluke/oh-my-agent | Skill | 1.4k | yesterday | MIT | A | 30 | Claude Code |
| pkf-writingPrismer-AI/PrismerCloud | Skill | 1.4k | 15d ago | MIT | A | 78 | Claude Code, Codex |
| monorepo-managementwshobson/agents | Skill | 42k | yesterday | MIT | C | 54 | Claude Code |
| render-3d-product-showcasegooseworks-ai/goose-skills | Skill | 1.3k | 10d ago | MIT | A | 159 | Claude Code, Codex |
| render-airdrop-carouselgooseworks-ai/goose-skills | Skill | 1.3k | 10d ago | MIT | A | 207 | Claude Code, Codex |