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 reggiechan74/JobOps --skill investigation-prepgit 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/investigation-prep)<a href="https://agentmods.dev/skills/reggiechan74/jobops/investigation-prep"><img src="https://agentmods.dev/badge/skills/reggiechan74/jobops/investigation-prep/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/reggiechan74/jobops/investigation-prep"><img src="https://agentmods.dev/badge/skills/reggiechan74/jobops/investigation-prep.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00013 | $0.06971 |
| Opus 5 | $0.00006 | $0.03485 |
| Sonnet 5 | $0.00003 | $0.01394 |
| Haiku 4.5 | $0.00001 | $0.00697 |
Grade A, and why
investigation-prep 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 — 1,015 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 workplace investigation framework.
Key Ontario Investigation Context:
- Bill 168 (Workplace Violence/Harassment): Ontario employers must investigate harassment complaints and inform parties of results
- OHSA Requirements: Occupational Health and Safety Act mandates investigation of workplace harassment complaints
- Human Rights Tribunal of Ontario (HRTO): External discrimination complaints are handled by HRTO, not internal HR
- Ministry of Labour: May investigate OHSA violations, health and safety complaints
- No Weingarten Rights for Non-Union: Unlike US union employees, non-unionized Ontario employees have no statutory right to representation during investigative interviews (union employees may have collective agreement protections)
Ontario Employer Obligations:
- Must investigate harassment complaints and inform complainant of results
- Must keep investigation confidential to extent possible
- Must not penalize employees for participating in investigations
- Must take appropriate corrective action based on findings
For US users: Specify --jurisdiction=US. US employees may have Weingarten rights (union), EEOC investigations, and state-specific protections.
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 investigations (potential termination, discrimination claims, serious allegations), recommend consultation with an employment attorney.
- Cooperation Balance: The goal is to protect your rights while cooperating appropriately with legitimate investigations.
- Confidentiality Reminder: Investigation discussions are typically confidential. Be cautious about what you share outside this process.
- Documentation: Keep personal notes of all investigation-related interactions.
- No Interference: Never obstruct an investigation through evidence destruction, witness tampering, or dishonesty.
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 · 1,015 lines · 13 tokens per session scan A 1632b258e51a
investigation-prep is a skill published in the GitHub repository reggiechan74/JobOps (25 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 6,971 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
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…