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/agy-researcherWrote 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/agy-researcher)<a href="https://agentmods.dev/skills/keli-wen/agy-staff/agy-researcher"><img src="https://agentmods.dev/badge/skills/keli-wen/agy-staff/agy-researcher/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/agy-researcher"><img src="https://agentmods.dev/badge/skills/keli-wen/agy-staff/agy-researcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 6 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.
- medium Agent Snooping · line 14 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.00077 | $0.00990 |
| Opus 5.5 | $0.00031 | $0.00396 |
| Sonnet 5.5 | $0.00015 | $0.00198 |
| Haiku 4.5 | $0.00008 | $0.00099 |
Grade A, and why
agy-researcher 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 24d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agy researcher
Delegate a research task to the agy staffer via the shared companion script. You are a thin shell: build the command, run it, return agy's report verbatim.
Locating the companion
This skill file lives at <plugin-root>/opencode-skills/agy-researcher/SKILL.md; resolve the companion path relative to this skill directory:
node "<skill-dir>/../../companion/agy-companion.mjs" research [flags] --prompt "what to research"
Pass the user's research topic verbatim via --prompt; use --prompt-file <path> or --stdin for a long brief.
[!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:
../agy-jobs/references/troubleshooting.md.
Collecting the result
The command returns a job id. Read ../agy-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)
--continue— reuse the last research conversation (quota-friendly, served largely from cache);--conversation <id>targets a specific one.--model <id>or--effort low|medium|high— default model isgemini-3.8-flash-high.--restricted/--unrestricted— permission profile. research defaults to unrestricted, so it works out of the box with no setup.--restrictedis the opt-in hardening path: agy runs without--dangerously-skip-permissionsand may only use allowlisted tools, so it needs the setup flow's evidence-gathering allowlist to be useful — and some native agy tools ignore allow-rules headless, so restricted runs can still come back empty.--prompt <text>/--prompt-file <path>/--stdin— the task, from exactly one of these three sources. Use file/stdin for long prompts.--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.
- 24d ago Changed · -2 tokens per session 2662ac2567f4
- 1mo ago Changed e7ed304d7ef7
- 1mo ago Changed · -2 lines a83adba7469e
- 1mo ago First seen · 54 lines · 79 tokens per session scan A 662ca7950a24
agy-researcher is a skill published in the GitHub repository keli-wen/agy-staff (795 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 990 once invoked, about $0.0003 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-09-05.
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.