Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/keli-wen/agy-staffnpx agentmods add skills/keli-wen/agy-staff/stafferWrote 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/staffer)<a href="https://agentmods.dev/skills/keli-wen/agy-staff/staffer"><img src="https://agentmods.dev/badge/skills/keli-wen/agy-staff/staffer/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/staffer"><img src="https://agentmods.dev/badge/skills/keli-wen/agy-staff/staffer.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 18 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.00121 | $0.00989 |
| Opus 5.5 | $0.00048 | $0.00396 |
| Sonnet 5.5 | $0.00024 | $0.00198 |
| Haiku 4.5 | $0.00012 | $0.00099 |
Grade A, and why
staffer 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 1mo 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agy staffer
The general-purpose persona: a clean entry point for tasks that none of the specialists fit. Its prompt template is deliberately minimal — the task text, the environment (cwd, branch, date), and the safety guardrails, nothing else. No role framing, no rules, no output format: the task defines its own output, and no unrelated template context can pull the run off course.
Prefer a specialist when one fits: researcher for surveys and deep dives, reviewer for second opinions on code or plans, implementer for edits to the working tree, ask for a cheap one-shot question.
staffer is also the route to agy-native tools no specialist covers — notably image generation: agy ships a generate_image tool (verified on v1.1.15; a 1024×1024 PNG in ~30s). Name the output path in the task, e.g. staffer --prompt "generate a pixel-art robot mascot, save it as assets/mascot.png".
Locating the companion
This skill file lives at <plugin-root>/skills/staffer/SKILL.md; resolve the companion path relative to this skill directory:
node "<skill-dir>/../../companion/agy-companion.mjs" staffer [flags] --prompt "task"
Pass the user's task text verbatim via --prompt; use --prompt-file <path> or --stdin for long text.
[!IMPORTANT] Run this command unsandboxed — agy needs a localhost port and its OAuth token file, which harness sandboxes hide. In Codex, request escalated permissions for the command. Details:
../jobs/references/troubleshooting.md.
Collecting the result
The command returns a job id. Read ../jobs/SKILL.md for result collection and recovery: dispatch, wait for the final result, then validate as needed. Do not proactively observe progress, read logs or inspect intermediate artifacts while running. Observe only when the user explicitly asks for progress; diagnose a failure or a result requiring intervention under the jobs protocol.
Flags (all optional)
--prompt <text>/--prompt-file <path>/--stdin— the task, from exactly one of these three sources. Use file/stdin for long prompts instead of shell quoting.--model <id>or--effort low|medium|high— default model isgemini-3.8-flash-medium.--restricted/--unrestricted— permission profile; staffer defaults to unrestricted like the other tool-using personas,--restrictedis the opt-in hardening path.--continue(or--conversation <id>),--timeout <dur>(default 60m, maximum 120m hard execution limit).
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.
- 1mo ago Changed bce6672f6e34
- 1mo ago Changed · -2 lines d84c6f778c66
- 1mo ago Changed 7e44e3e325f7
- 1mo ago First seen · 50 lines · 121 tokens per session scan A 432af178e2be
staffer is a skill published in the GitHub repository keli-wen/agy-staff (795 stars, last pushed 3d ago), licensed MIT. It adds 121 tokens to every session and 989 once invoked, about $0.0005 per session on Opus 5.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
moragent
Lead protocol for running MORAGENT crews with specs, task dispatch, memory and brain sync.
moragent-memory
Decide what belongs in MORAGENT canonical, episodic, transient and procedural memory, and when to promote it.
moragent-spec
Drive spec-driven development phases with mora spec next, EARS requirements, design and tasks.
moragent-worker
Worker protocol for receiving scoped MORAGENT tasks, using context, verifying work and reporting done or blocked.
mantis-reproduce
Generates and runs crash reproducers to verify security flaws. Use when viable findings exist and you need to write and execute a script or payload to verify the crash. Don't use for code auditing or patching.
mantis-meta-agent
Acts as the persistent supervisor, launching and monitoring the automated review campaign. Use when running a long-running, continuous security review campaign that needs autonomous coordination. Don't use for executing individual review stages directly.