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 keli-wen/agy-staff --skill jobsgit clone --depth 1 https://github.com/keli-wen/agy-staffWrote 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/keli-wen/agy-staff/jobs)<a href="https://agentmods.dev/skills/keli-wen/agy-staff/jobs"><img src="https://agentmods.dev/badge/skills/keli-wen/agy-staff/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/keli-wen/agy-staff/jobs"><img src="https://agentmods.dev/badge/skills/keli-wen/agy-staff/jobs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 16 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00099 | $0.02150 |
| Opus 5 | $0.00049 | $0.01075 |
| Sonnet 5 | $0.00020 | $0.00430 |
| Haiku 4.5 | $0.00010 | $0.00215 |
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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- agy-jobs — 92% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agy jobs
Manage background staffer/research/review/implement jobs. State is per repository in .agy-staff/. Only ask runs synchronously.
This file lives at <plugin-root>/skills/jobs/SKILL.md:
node "<skill-dir>/../../companion/agy-companion.mjs" <command> [args]
Collect the result
Default flow: prepare the prompt → dispatch → wait for the final result → validate as needed. While a job is running, do not proactively call observe/status, read logs or inspect intermediate artifacts. Do not query progress for routine updates or create sleep/observe loops. Observe only when the user explicitly asks for progress; diagnose after receiving a failure or a result requiring intervention.
- Keep the returned job id. Start
wait <id> --timeout 10min the background, using the same unsandboxed context as launch. Use a separate wait for each job; never wait for several jobs serially in one shell. - For wait, branch on the exit code:
| Code | Meaning | Next action |
|---|---|---|
| 0 | Invocation ended; response text delivered | Assess whether it satisfies the task. Review attached diagnostics; inspect further only as needed. |
| 2 | Still running; wait soft-expired | Wait again for the same job. The attached snapshot is not a request to inspect progress or intervene. |
| 3 | Error or crash | Read the error and recovery information below. |
| 4 | Canceled | Complete any already-authorized follow-up; otherwise report cancellation. |
| 5 | Attention: resumable timeout | Inspect partial workspace changes; ask whether to continue with the suggested timeout or stop. Continue only after explicit user confirmation. |
| 1 | Invalid command or other command error | Quote the error and correct the named problem. |
done describes invocation and response delivery, not task acceptance. Preserve agy-cli response text and diagnostics; a nonempty response may only acknowledge launched background work. Successful calls with warnings include a bounded log tail on stderr and a full-log pointer. The orchestrator assesses the response and artifacts, uses observe or diagnostics if the returned result needs investigation, and decides whether to propose continuation. Keep the recovery confirmation rules below; do not infer timeout from response wording or add routine progress polling.
What ships with it
2 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.
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.
- yesterday Changed · +10 lines 38de55f3c805
- 2d ago Changed · +5 lines 66539c0da0db
- 3d ago Changed · +13 lines cfa91c62046d
- 7d ago Changed · +2 lines 578587438484
- 12d ago First seen · 54 lines · 99 tokens per session scan A 3f9ecaa33b2a
jobs is a skill published in the GitHub repository keli-wen/agy-staff (131 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 2,150 once invoked, about $0.0005 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
mantis-configure
Configures and validates Mantis pipeline environments, sandbox mechanisms, and AI models. Use to set up workflow.json, auto-detect host capabilities, switch between sandboxes (static-only, gvisor, microsandbox, gce), select AI models, and run fast 1-2s preflight tests. Don't use for scanning source code or running…
party
Throw or join an agents-party: a shared channel where several AI agent sessions (and their humans) talk to each other — Claude Code, Cursor, Codex or any other agent, on one machine or across machines. Use when the user asks to throw or start a party, wants several agent sessions to collaborate in one chat, wants two…
cc-status
A structured workflow for checking Codex configuration, task status, synchronization results, and project .codex task records.
notify-user
Telegram comms playbook for Antigravity — when and how to reply, ack long work, present choices, and delegate to other agents. Use whenever you're paired to a Telegram chat via the telegram-agy MCP server and need to talk back to the user. The chat is your only signal channel — terminal output never reaches the user.
generate-daily-schedule
Use when turning a day's structured inputs — fixed commitments, tasks, and free windows — into a concrete 15-minute schedule. Domain-agnostic; the caller provides all context.
token-efficiency
Token conservation economics, bounded context-window pruning, AST structural query optimization, and high-precision prompt budget discipline.