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/huskar20/huskar20-plugins/setupnpx skills add huskar20/huskar20-plugins --skill setupgit clone --depth 1 https://github.com/huskar20/huskar20-pluginsWhat 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 | $0.00096 | $0.03368 |
| Opus 5 | $0.00048 | $0.01684 |
| Sonnet 5 | $0.00019 | $0.00674 |
| Haiku 4.5 | $0.00010 | $0.00337 |
Grade A, and why
setup 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 3d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Career Hunter — Setup
Onboard a new user end to end: interview → profile file → tracker spreadsheet →
automation config. Everything the apply and sync skills need is produced here.
Re-running setup is safe: offer to update the existing profile instead of starting over.
Outputs (all in the user's working folder)
| File | Purpose |
|---|---|
career-profile.md |
Canonical answers for every application form. The user edits it by hand afterward; other skills re-read it every run. |
career-hunter-state/config.json |
Spreadsheet ID, resume path, submission mode, caps, schedule, notification prefs. |
career-hunter-state/seen_jobs.json |
Created empty; the apply skill's dedupe memory. |
career-hunter-state/last_run.json |
Created with null fields; the sync skill's watermark. |
Step 1 — Check prerequisites
Verify each connector is actually present (list the available tools / connectors, don't assume), and tell the user plainly what is missing rather than failing later. A plugin cannot gate its own installation on connectors — this check is the real gate, so do it thoroughly and stop if a required piece is absent.
- Gmail connector — needed by sync (and apply, for email verification codes).
- Google Drive connector — creates the tracker spreadsheet by copying the
published template (
copy_file) and reads it for dedupe in apply/sync. - Google Calendar connector — needed so sync can create an event when it detects a confirmed interview. If it's missing, say so; the user can still proceed (sync will fall back to notification-only) but flag it as a TODO.
- Claude-in-Chrome extension, connected —
list_connected_browsers; writes application rows and fills application forms, in the user's own Chrome session. Setup itself no longer needs it for the tracker (the template copy brings the structure with it), but apply and sync do — there is no Sheets-cell MCP, so every cell write goes through Chrome. If it's missing, setup can still finish; flag it as a TODO. - Resume file — ask the user to place their resume PDF in the working folder (or a subfolder) and confirm its path. Record it in config. If they don't have it ready, continue setup and leave a TODO in the summary.
What ships with it
2 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.
- 3d ago First seen · 242 lines · 96 tokens per session scan A fc508f0c519e
setup is a skill published in the GitHub repository huskar20/huskar20-plugins (3 stars, last pushed 19d ago), licensed MIT. It adds 96 tokens to every session and 3,368 once invoked, about $0.0005 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
organize-threads
猫猫辅助整理未分类 thread，分析标题和元数据，建议合适的标签。 Use when: 用户说"帮我整理"、"分类 thread"、点击整理按钮。 Not for: 删除/编辑标签本身。 Output: 按 thread 的标签建议列表。.
change-keybinding
Customize Warp keyboard shortcuts (keybindings, keymappings) by editing the user's keybindings.yaml file. Use when the user asks to remap a key combination, rebind an action, change a shortcut, or remove a default keybinding (e.g. "change ctrl+space to ctrl+s", "rebind the command palette to cmd+p", "remove the…