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 tmargolis/career-navigator --skill daily-schedulegit clone --depth 1 https://github.com/tmargolis/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/daily-schedule)<a href="https://agentmods.dev/skills/tmargolis/career-navigator/daily-schedule"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/daily-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/daily-schedule"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/daily-schedule.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
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 →
- medium Agent Snooping · line 24 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Excessive Agency · line 56 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 79 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00067 | $0.02654 |
| Opus 5 | $0.00034 | $0.01327 |
| Sonnet 5 | $0.00013 | $0.00531 |
| Haiku 4.5 | $0.00007 | $0.00265 |
Grade A, and why
daily-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 10d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scheduling (Claude Cowork)
This skill is designed to run as a daily scheduled task using Cowork’s /schedule (or equivalent). Example payload the user might schedule:
Run the Career Navigator
daily-scheduleskill for my job search folder. Deliver the daily brief perskills/daily-schedule/SKILL.md.
After the first successful run, Cowork typically refines the scheduled prompt with learned paths, connectors, and context.
Workflow
1. Resolve {user_dir} and validate data files
Check:
{user_dir}/CareerNavigator/profile.md{user_dir}/CareerNavigator/ExperienceLibrary.json{user_dir}/CareerNavigator/tracker.json{user_dir}/CareerNavigator/artifacts-index.json{user_dir}/CareerNavigator/StoryCorpus.json(create-on-demand is allowed viamine-stories)
If missing, output:
Daily brief skipped: run
/career-navigator:launchto initialize Career Navigator.
2. Reconcile artifacts before summary
Before computing the brief, scan {user_dir} for any PDF/DOCX artifacts.
If one or more artifact files are present, run artifact-saved first so
artifacts-index.json is synchronized before counts are calculated.
If no artifacts are found, continue without running artifact-saved.
2.5 Auto-ingest new source documents
Before finalizing the brief, detect whether newly discovered resume/CV-style files are present in {user_dir} but not yet represented as source entries in ExperienceLibrary.
When such files are found:
- Automatically run
add-sourcefor each newly discovered source document (no manual prompt required). - After each successful ingest, re-run
artifact-savedonce to keepartifacts-index.jsonconsistent. - In the final brief, include a one-line note listing how many files were auto-ingested.
If an ingest fails for any file:
- Continue with the daily brief.
- List failed filenames under a short "Needs attention" line.
- Recommend rerunning
/career-navigator:add-sourcefor those specific files.
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.
- 10d ago First seen · 211 lines · 67 tokens per session scan A 617f5a672687
daily-schedule is a skill published in the GitHub repository tmargolis/career-navigator (13 stars, last pushed 11d ago), licensed Apache-2.0. It adds 67 tokens to every session and 2,654 once invoked, about $0.0003 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-30.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.