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/audit-sourcenpx skills add reggiechan74/JobOps --skill audit-sourcegit 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/audit-source)<a href="https://agentmods.dev/skills/reggiechan74/jobops/audit-source"><img src="https://agentmods.dev/badge/skills/reggiechan74/jobops/audit-source.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.00026 | $0.03963 |
| Opus 5 | $0.00013 | $0.01982 |
| Sonnet 5 | $0.00005 | $0.00793 |
| Haiku 4.5 | $0.00003 | $0.00396 |
Grade A, and why
audit-source 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 5d 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 — 319 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.resume_source for the source folder root.
The canonical layout contract lives at {plugin_root}/skills/audit-source/source_layout.md. Read it before running checks — the contract evolves; do not rely on memory.
Flags
--deep— also run semantic checks (achievements without metrics, vague responsibilities, cross-file skill inconsistencies). Slower, more questions. Default off.--migrate-layout— interactively reorganize an existing folder into the canonical layout. Run once at adoption time. Refuses to run if layout already matches.--section=<path>— audit only the named subfolder (e.g.WorkHistory/). Default: whole tree.--dry-run— produce the gap report without prompting for fills or writing edits.
Your Task
Audit the source folder so downstream skills can rely on it as authoritative — no inference, no hallucination, no synthesized fields. Every gap is either filled with user-authored content or explicitly marked as known-incomplete.
The remaining sections (Step 1 through Step 5, and "What this skill MUST NOT do") follow.
Step 1: Layout check
Read {plugin_root}/skills/audit-source/source_layout.md for the canonical structure. Then walk config.directories.resume_source and compare.
For each REQUIRED file in the canonical layout, check existence. For each file in the source folder, check whether its path matches the canonical layout.
Produce a layout diff:
| Status | Canonical path | Found at |
|---|---|---|
| OK | Identity/Name.md | Identity/Name.md |
| MISSING | Identity/CurrentRole.md | (not found) |
| MISLOCATED | Technology/TechStack.md | Skills.md (root) |
Decision tree:
- All canonical-required files present AND no mislocated files, WITHOUT
--migrate-layout→ proceed to Step 2. - All canonical-required files present AND no mislocated files, WITH
--migrate-layout→ print "Layout already matches canonical contract; no reorganization needed." and stop. - Missing files OR mislocated files present, WITHOUT
--migrate-layout→ print the diff and stop. Tell the user: "Layout does not match canonical contract. Re-run with--migrate-layoutto interactively reorganize, or fix manually and re-run." - Missing files OR mislocated files present, WITH
--migrate-layout→ enter Step 1a (migration).
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- source_layout.md 3.6 KB
- tests/baseline_broken_folder.md 4.6 KB
- tests/fixtures/broken_folder/Identity/CurrentRole.md 76 B
- tests/fixtures/broken_folder/Identity/Name.md 15 B
- tests/fixtures/broken_folder/Preferences/AntiVision.md 118 B
- tests/fixtures/broken_folder/Preferences/Vision.md 153 B
- tests/fixtures/broken_folder/Technology/Certifications.md 68 B
- tests/fixtures/broken_folder/Technology/TechStack.md 72 B
- tests/fixtures/broken_folder/WorkHistory/01_globex.md 258 B
- tests/fixtures/broken_folder/WorkHistory/02_initech.md 266 B
- tests/GREEN_RESULTS.md 4.1 KB
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.
- 5d ago First seen · 319 lines · 26 tokens per session scan A 177ba084eb9a
audit-source is a skill published in the GitHub repository reggiechan74/JobOps (25 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 3,963 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…