Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add tmargolis/career-navigator/plugin install career-navigatorWrote 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/tmargolis/career-navigator/setup-schedule)<a href="https://agentmods.dev/skills/tmargolis/career-navigator/setup-schedule"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/setup-schedule/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/tmargolis/career-navigator/setup-schedule"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/setup-schedule.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.00072 | $0.03073 |
| Opus 5.5 | $0.00029 | $0.01229 |
| Sonnet 5.5 | $0.00014 | $0.00615 |
| Haiku 4.5 | $0.00007 | $0.00307 |
Grade A, and why
setup-schedule 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 29d 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create or update the Career Navigator daily brief as a Cowork scheduled task. When the task fires each morning, it delivers a full operating brief: pipeline digest, Gmail inbox scan (two-pass strategy to catch missed status emails), follow-up alerts, and top new job recommendations appended to recommendations.json.
1. Verify Career Navigator setup
Read {user_dir}/CareerNavigator/profile.md.
If the profile is missing, output:
Daily schedule not set up: run
/career-navigator:launchfirst to initialize Career Navigator.
Then stop.
2. Check for existing scheduled tasks
Load and call mcp__scheduled-tasks__list_scheduled_tasks. Look for a task named career-navigator-daily-brief and a task named career-navigator-pipeline-refresh (or whose prompt otherwise mentions Career Navigator).
If the daily brief task is found:
- Display its current schedule and a one-line summary of its prompt
- Ask: "A daily brief is already scheduled. Would you like to update the time, update the prompt, or keep it as-is?"
- If the user wants to update: follow Steps 3–5 but use
mcp__scheduled-tasks__update_scheduled_taskwith the existing task's ID instead of creating a new one - If the user wants to keep it: confirm "Your daily brief is already scheduled." and continue to check the pipeline-refresh task below rather than stopping
If the pipeline-refresh task is found: display its current schedule and offer the same update/keep choice, using update_scheduled_task if the user wants a change.
If both tasks already exist and the user wants to keep both as-is, confirm "Your daily brief and pipeline refresh are already scheduled." and stop.
3. Confirm preferred schedule(s)
Ask: "What time would you like your daily brief? Default is 7:00 AM daily."
Accept natural language and convert to a cron expression:
| Input | Cron |
|---|---|
| "7am" / "7:00 AM" / default | 0 7 * * * |
| "6:30am" | 30 6 * * * |
| "8am weekdays" | 0 8 * * 1-5 |
| "6am every day" | 0 6 * * * |
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.
- 29d ago Changed · +43 lines · +14 tokens per session e072e57b1f11
- 1mo ago First seen · 262 lines · 58 tokens per session scan A dbfe5ce16c39
setup-schedule is a skill published in the GitHub repository tmargolis/career-navigator (16 stars, last pushed 27d ago), licensed Apache-2.0. It adds 72 tokens to every session and 3,073 once invoked, about $0.0003 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.
Other skills, from other repositories
gsd-ns-manage
Invoke this Pi skill with /skill:gsd-ns-manage.
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
to-spec
A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…