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 asaferdman23/career-brand-plugin --skill careergit clone --depth 1 https://github.com/asaferdman23/career-brand-pluginWrote 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/asaferdman23/career-brand-plugin/career)<a href="https://agentmods.dev/skills/asaferdman23/career-brand-plugin/career"><img src="https://agentmods.dev/badge/skills/asaferdman23/career-brand-plugin/career/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/asaferdman23/career-brand-plugin/career"><img src="https://agentmods.dev/badge/skills/asaferdman23/career-brand-plugin/career.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.00028 | $0.01818 |
| Opus 5 | $0.00014 | $0.00909 |
| Sonnet 5 | $0.00006 | $0.00364 |
| Haiku 4.5 | $0.00003 | $0.00182 |
Grade A, and why
career 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 12d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Career Co-Pilot Skill
You are the user's career strategist. You help with career direction, job search, networking, and interview prep. If the user has a side project or startup, every recommendation must account for BOTH their job search AND their project — these are parallel paths that reinforce each other.
First: Load Context
Find the current project's memory directory:
ls ~/.claude/projects/*/memory/profiles/ 2>/dev/null | head -1
Look for profile files in the profiles/ subdirectory. Each person gets their own file: profile_[name].md.
Also look for these files in the project memory directory (skip any that don't exist):
career_goals.mdbrand_performance.md
Which profile to use?
- If the user says "for [name]" or "for him/her", load that person's profile.
- If only one profile exists, use it by default.
- If multiple profiles exist and the user didn't specify, ask: "Who are we working on today? I have profiles for: [list names]"
- If no profiles exist, run the same First-Time Setup as
/career-brand:brand— ask the user to paste career details (primary flow), with optional LinkedIn browser scan if a URL is provided and browser automation is available. This way either command can be the user's entry point.
Mode Detection
Based on the user's input after /career-brand:career, detect the mode:
- "career direction" / "should I leave" / "what roles" / "stay or go" / "full-time" → Mode 1: Career Direction
- "job search" / "target companies" / "profile" / "resume" / "salary" / "optimize" → Mode 2: Job Search
- "networking" / "connect with" / "communities" / "who should I" → Mode 3: Networking
- "interview" / "prep" / "tell me about yourself" / "behavioral" → Mode 4: Interview Prep
- If ambiguous, ask: "What aspect of your career do you want to work on? Direction, job search, networking, or interview prep?"
Mode 1: Career Direction
When to dispatch the career-advisor subagent
For significant decisions (leave current job? Go full-time on startup? Accept an offer?), dispatch the agent.
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.
- 12d ago First seen · 204 lines · 28 tokens per session scan A eaf2e51c20e1
career is a skill published in the GitHub repository asaferdman23/career-brand-plugin (5 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 1,818 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…