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 get-vix/vix --skill jobsgit clone --depth 1 https://github.com/get-vix/vixWrote 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/get-vix/vix/jobs)<a href="https://agentmods.dev/skills/get-vix/vix/jobs"><img src="https://agentmods.dev/badge/skills/get-vix/vix/jobs/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/get-vix/vix/jobs"><img src="https://agentmods.dev/badge/skills/get-vix/vix/jobs.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.00046 | $0.01980 |
| Opus 5 | $0.00023 | $0.00990 |
| Sonnet 5 | $0.00009 | $0.00396 |
| Haiku 4.5 | $0.00005 | $0.00198 |
Grade A, and why
jobs 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 9d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 9d ago First seen · 153 lines · 46 tokens per session scan A b16b9f12ddf3
jobs is a skill published in the GitHub repository get-vix/vix (275 stars, last pushed 3d ago), licensed AGPL-3.0. It adds 46 tokens to every session and 1,980 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
commit
Inspect git status, draft a commit message that matches the repo's style, and commit staged changes.
review
Review a change for correctness, security, and missing tests.
heartbeat
Periodic heartbeat check that reads HEARTBEAT.md from the workspace and executes any tasks listed there. Use for autonomous background monitoring, periodic maintenance, and proactive task execution. Triggered by a cron schedule.
review
Review current code changes for bugs, regressions, test gaps, and project-guideline violations.
oculpm-journal
A work-journal format for recording coding-agent tasks, including bugs, features, errors, refactors, and chores. It defines where files go and what information each record must contain.
find-key-internal-sources
Use when a seller needs to find the best internal experts, owners, approvers, documents, channels, source-of-truth materials, or escalation routes for a customer question, product topic, competitive objection, implementation issue, account task, or other sales-support need. Route questions such as 'who knows about…