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/syncnpx skills add huskar20/huskar20-plugins --skill syncgit clone --depth 1 https://github.com/huskar20/huskar20-pluginsWrote 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/huskar20/huskar20-plugins/sync)<a href="https://agentmods.dev/skills/huskar20/huskar20-plugins/sync"><img src="https://agentmods.dev/badge/skills/huskar20/huskar20-plugins/sync.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 | $0.00092 | $0.01411 |
| Opus 5 | $0.00046 | $0.00705 |
| Sonnet 5 | $0.00018 | $0.00282 |
| Haiku 4.5 | $0.00009 | $0.00141 |
Grade A, and why
sync 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Career Hunter — Sync
Reconcile recent Gmail with the tracker: detect application events from email, write them into the sheet, notify on interviews.
Load configuration first
From the working folder (missing → route to career-hunter: setup):
career-hunter-state/config.json—spreadsheet_id,spreadsheet_url,push_on_interview,create_calendar_events.career-hunter-state/last_run.json—{ "last_run_utc": "...", "last_run_date": "YYYY/MM/DD", "note": "..." }(noteis the previous run's summary, written in step 6). Missing, unreadable, or null fields → default to the last 7 days and say so.- The user's email address (from
career-profile.md) — needed to detect replies.
Workflow
1. Search Gmail for the window
Use the Gmail connector search_threads with after:<last_run_date> plus a
broad OR of application keywords: application OR applied OR "thank you for applying" OR recruiter OR "your application" OR candidate OR interview OR position OR role OR hiring OR offer OR "moving forward" OR "next steps" OR unfortunately OR assessment. Request minimal view first to scan snippets
cheaply; pull full content only for threads that look like real events (fall
back to metadata-only if a thread is too large).
2. Classify — signal vs. noise
Keep (real events):
- Application confirmations ("we received your application") → Stage
Applied, StatusApplied. - Rejections ("decided to proceed with other candidates", "unfortunately") →
Stage
Closed, StatusRejected. - Interview/next-step invites, availability requests, confirmations, reschedules → update Stage/Status/Interview Date/Next Step accordingly.
- Recruiter outreach only if the user has actually engaged (see policy).
Discard as noise (never add rows):
- Cold recruiter outreach with no reply — especially LinkedIn InMails and staffing-agency cold emails.
- Job-board alerts ("You may be a fit for…", posting digests), "your application was viewed" notices (no stage change), ATS marketing (e.g. Greenhouse "Dream Job"), newsletters, promos.
What ships with it
1 file 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 · 117 lines · 92 tokens per session scan A 11fd1422f846
sync is a skill published in the GitHub repository huskar20/huskar20-plugins (3 stars, last pushed 19d ago), licensed MIT. It adds 92 tokens to every session and 1,411 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
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
gog
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
google-workspace
Access Google Workspace APIs (Drive, Docs, Calendar, Gmail, Sheets, Slides, Chat, People) via local helper scripts without MCP. Handles OAuth login and direct API calls.
wecomcli-sheet
企业微信在线表格文档管理：新建在线表格、导入 CSV/Excel 为在线表格、读取表格信息与数据、修改表格内容、追加行数据、子表管理。当用户提到'表格'、'在线表格'、'excel表格'这些关键词触发，或链接形如 https://doc.weixin.qq.com/sheet/xxx 时触发。文档公共操作请使用 wecomcli-doc-manage；doc文档操作请使用 wecomcli-doc；智能表格内容 CRUD 请使用 wecomcli-smartsheet。.
feishu-tools
Use the Feishu/Lark plugin MCP tools for Feishu documents, spreadsheets, knowledge content, and other matching workspace operations.
feishu
Use when the user mentions 飞书 / Feishu / Lark workspace operations: docx (云文档) read/write, bitable (多维表格) records / views / dashboards, drive (云盘) upload/download, wiki (知识库) link resolution, approval (审批) instance create/cancel/query, calendar (日历) event create/list/update + attendees, contact (联系人) user/department…