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/reggiechan74/jobops/code-rednpx skills add reggiechan74/JobOps --skill code-redgit clone --depth 1 https://github.com/reggiechan74/JobOpsWhat 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.00017 | $0.05520 |
| Opus 5 | $0.00009 | $0.02760 |
| Sonnet 5 | $0.00003 | $0.01104 |
| Haiku 4.5 | $0.00002 | $0.00552 |
Grade A, and why
code-red 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 2d 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 — 797 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration
Read .jobops/config.json. If missing, stop with:
JOBOPS NOT CONFIGURED Run /jobops:setup to initialize your workspace.
Use config.directories.<key> for all file paths in this skill.
Use config.preferences.cultural_profile if this skill generates resume-style content.
Use config.preferences.default_jurisdiction if this skill has jurisdiction-sensitive logic (crisis/legal skills accept --jurisdiction=<ISO-3166-2> to override).
Default Jurisdiction: Ontario, Canada
This command defaults to Ontario, Canada employment law framework. Key principles:
- No At-Will Employment: Unlike US states, Canadian employees cannot be terminated without cause or reasonable notice (common law or statutory)
- Notice Periods: Employees entitled to common law reasonable notice (often 1 month per year of service, up to 24 months) OR Employment Standards Act (ESA) minimums
- Just Cause: Employers must prove serious misconduct for termination without notice - a very high bar
- Human Rights: Ontario Human Rights Code protects against discrimination (broader protections than US federal law)
- Constructive Dismissal: Significant changes to job duties, compensation, or working conditions may constitute wrongful dismissal
For US users: Specify --jurisdiction=US or mention your state. US employment is generally at-will with different statutory frameworks (Title VII, ADEA, ADA).
Important Disclaimers
CRITICAL: Read these disclaimers ALOUD to the user at session start:
- Not Legal Advice: This guidance is strategic, not legal. For legally complex situations (discrimination claims, wrongful termination, harassment), recommend consultation with an employment attorney.
- No Outcome Guarantees: Employment situations are unpredictable. Strategies improve positioning but cannot guarantee results.
- Confidentiality Reminder: Be cautious about what you share. This conversation may be discoverable in legal proceedings.
- Documentation: Save all workplace communications. BCC personal email where appropriate.
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.
- 2d ago First seen · 797 lines · 17 tokens per session scan A c30bf6862eea
code-red is a skill published in the GitHub repository reggiechan74/JobOps (25 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 5,520 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-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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.