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/github-portfolionpx skills add reggiechan74/JobOps --skill github-portfoliogit clone --depth 1 https://github.com/reggiechan74/JobOpsWrote 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/reggiechan74/jobops/github-portfolio)<a href="https://agentmods.dev/skills/reggiechan74/jobops/github-portfolio"><img src="https://agentmods.dev/badge/skills/reggiechan74/jobops/github-portfolio.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.00014 | $0.04093 |
| Opus 5 | $0.00007 | $0.02047 |
| Sonnet 5 | $0.00003 | $0.00819 |
| Haiku 4.5 | $0.00001 | $0.00409 |
Grade A, and why
github-portfolio 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 3d 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 — 485 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).
Usage and Arguments
Creates or updates a GitHub portfolio document.
Output file: {config.directories.career_analysis}/github_portfolio_{YYYYMMDD}.md — a fresh timestamped snapshot is written on every run (create, add, or refresh).
Usage forms:
/github-portfolio <repository-url>— create if no prior snapshot exists, otherwise add the repo to the latest snapshot./github-portfolio <repository-url> -create— force a brand-new snapshot (first repository)./github-portfolio <repository-url> -update— add the repository to the latest existing snapshot./github-portfolio -update— full portfolio refresh/reorganization of the latest snapshot (no URL needed).
Arguments:
$1: Repository URL (required for adding repositories) OR the-updateflag for refresh-only mode.$2: Mode flag (optional, defaults to auto-detect):-create: Force create a new portfolio snapshot.-update: Force update of the latest portfolio snapshot.
Step 1: Parse Arguments and Determine Mode
Repository URL: $1 Mode Flag: ${2:-auto}
Checking arguments:
- If
$1is-updateand no$2: Refresh Mode (reorganize existing portfolio) - If
$1is a URL: Repository Addition Mode (create or update)- If portfolio exists: Update mode
- If portfolio doesn't exist: Create mode
- Mode can be forced with
$2flag
Step 2: Check Portfolio Existence
Checking whether a prior portfolio snapshot already exists in {config.directories.career_analysis}/ (any file matching github_portfolio_*.md). When more than one exists, use the most recent by date suffix as the working snapshot for add/refresh operations.
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.
- 3d ago First seen · 485 lines · 14 tokens per session scan A 7e7db54a1133
github-portfolio is a skill published in the GitHub repository reggiechan74/JobOps (25 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 4,093 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.
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…