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 agentmods add skills/pleaseai/run-verify-plugin/run-skill-generatornpx skills add pleaseai/run-verify-plugin --skill run-skill-generatorgit clone --depth 1 https://github.com/pleaseai/run-verify-pluginWrote 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/pleaseai/run-verify-plugin/run-skill-generator)<a href="https://agentmods.dev/skills/pleaseai/run-verify-plugin/run-skill-generator"><img src="https://agentmods.dev/badge/skills/pleaseai/run-verify-plugin/run-skill-generator.svg" alt="Measured on agentmods" 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 | $0.00065 | $0.04368 |
| Opus 5 | $0.00032 | $0.02184 |
| Sonnet 5 | $0.00013 | $0.00874 |
| Haiku 4.5 | $0.00006 | $0.00437 |
Grade A, and why
run-skill-generator scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
it's `curl`. You build (or script) that harness now, commit it How it starts
The opening of the file, as written. The whole thing — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your job is to produce a skill at <unit>/<skills-dir>/run-<unit-name>/
that lets a future agent build, launch, and drive this project from
a clean machine.
The skill has two parts that live together:
<unit>/<skills-dir>/run-<unit-name>/
SKILL.md ← agent-facing instructions — SHORT. Points at the driver.
driver.mjs ← (or driver.py, smoke.sh, … — or none: web apps use
an off-the-shelf headless-browser CLI, and the
heredoc in SKILL.md is the script)
That almost always means writing code, not just prose. If the app
has any interactive surface (GUI, TUI, long-running server, REPL), the
future agent needs a programmatic way to poke it. A markdown file by
itself cannot click a button — but sometimes the button-clicker
already exists: for web apps it's a headless-browser CLI, for servers
it's curl. You build (or script) that harness now, commit it
alongside the skill, and the SKILL.md documents how to use it.
Definition of done
You are done when all of these are true:
- You launched the app in this environment and interacted with it — not its test suite, the actual running app. For anything with a GUI, that means you have a screenshot file on disk that you took.
- The interaction harness is committed next to the skill. A driver
script, a REPL wrapper, a smoke test, or the headless-browser heredoc
inline in
SKILL.md— whatever you used to drive the app in step 1. (Graduated intoscripts//e2e/? — fine, point at it. Web app with an off-the-shelf browser CLI? — the inline script is the harness; no separate file.) - The
SKILL.mddocuments the harness as the primary agent path — the section a future agent reads first is "run this driver / pipe these commands to the browser CLI," not "runnpm startand a window opens." - Every code block in
SKILL.mdis a command you ran that worked. This session. This environment. Not from the README, not inferred.
If you're about to write the skill and you don't have (1), stop. You are about to paraphrase existing docs. That document already exists — it's called the README, and the whole reason you're here is that it wasn't enough.
What ships with it
1 file 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.
- 3d ago First seen · 357 lines · 65 tokens per session scan A 7e4e8d057f93
run-skill-generator is a skill published in the GitHub repository pleaseai/run-verify-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 4,368 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
jobs
Manage agy staffer background jobs - collect results, check status, cancel, follow-up conversation, and setup. Use when an agy job needs collecting, when the user asks "is the agy job done", "show agy's result", "cancel the agy job", "continue the agy conversation", or "set up agy". This is the orchestrator's skill…
researcher
Delegate a deep research or survey task to Google's Antigravity CLI (agy staffer, fast Gemini). Use when the user says /agy:researcher, "ask agy to research", "have the agy staffer survey X", or wants a second, independent deep-dive on a topic or codebase without spending the host model's quota.
staffer
Delegate a general-purpose task to Google's Antigravity CLI (agy staffer, fast Gemini) with a minimal, unopinionated prompt. Use when the user says /agy:staffer, "have agy do/handle X", "have agy generate an image", or the task fits none of the specialist personas (researcher / reviewer / implementer / ask) — the…
ask
Ask Google's Antigravity CLI (agy staffer, fast Gemini) a cheap one-shot question - the fast zero-tool mode and the post-install smoke test. Use when the user says /agy:ask, "ask agy", "quick second opinion from agy", or right after installing to verify the plugin works.
reviewer
Get a second-opinion review from Google's Antigravity CLI (agy staffer, fast Gemini) - of code (a diff, PR, working tree) or of a decision, plan, or design. Use when the user says /agy:reviewer, "have agy review this", "second opinion on my diff/PR/plan", or after finishing work and wanting an independent verifier…
gemini-swarm
Use BEFORE writing or editing code, tests, docs, or other content yourself — whenever the writing spans more than one file or more than 20 lines. Delegating the writing to Gemini sessions via the agy (Antigravity) CLI is the default; you orchestrate. Also use when the user asks to swarm/fan out/parallelize work across…