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/tmargolis/career-navigator/evaluate-postnpx skills add tmargolis/career-navigator --skill evaluate-postgit 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/evaluate-post)<a href="https://agentmods.dev/skills/tmargolis/career-navigator/evaluate-post"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/evaluate-post.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.00031 | $0.00296 |
| Opus 5 | $0.00015 | $0.00148 |
| Sonnet 5 | $0.00006 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
evaluate-post 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 4d 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.
What it actually says
Invoke writer in evaluate-post mode.
Invocation
- Use the exact agent name
writer. Retry once if invocation fails.
Workflow
- Read
{user_dir}/CareerNavigator/profile.md(Target Companies, Target Roles, industries). If targets are empty, ask once whether to evaluate against role-level norms only. - Collect the draft text from the user (or from the current turn).
- Instruct
writerto run the evaluate-post operation: risk tier, rationale vs each named target employer type, and optional safer paraphrases—user decides whether to edit. - If risk is high, suggest pausing publish until they adjust or run
content-suggestfor alternative angles.
Relation to cultural-risk-flag
When drafting in other flows triggers a risk check, prefer this skill’s rules so writer remains the single evaluator for public copy.
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.
- 4d ago First seen · 29 lines · 31 tokens per session scan A 7bee352e14d9
evaluate-post is a skill published in the GitHub repository tmargolis/career-navigator (14 stars, last pushed 5d ago), licensed Apache-2.0. It adds 31 tokens to every session and 296 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…