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 IgorGanapolsky/ThumbGate --skill programmatic-agent-runsgit clone --depth 1 https://github.com/IgorGanapolsky/ThumbGateWrote 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/igorganapolsky/thumbgate/programmatic-agent-runs)<a href="https://agentmods.dev/skills/igorganapolsky/thumbgate/programmatic-agent-runs"><img src="https://agentmods.dev/badge/skills/igorganapolsky/thumbgate/programmatic-agent-runs/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/igorganapolsky/thumbgate/programmatic-agent-runs"><img src="https://agentmods.dev/badge/skills/igorganapolsky/thumbgate/programmatic-agent-runs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.00456 |
| Opus 5 | $0.00015 | $0.00228 |
| Sonnet 5 | $0.00006 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
programmatic-agent-runs 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.
What it actually says
Programmatic Agent Runs
Use this skill before launching a coding agent through the Cursor SDK, Cursor cloud agents, self-hosted workers, or subagents.
When to use
- A task starts from code, CI, a backend service, a kanban automation, or any unattended workflow
- The run can edit files, push a branch, create a PR, publish a package, deploy, or call shell tools
- The run delegates work to subagents with different prompts, models, or scopes
Launch checklist
- Recall lessons with
search_lessonsfor the repo, branch, files, and intended action. - Check active gates with
prevention_rulesbefore enabling writes orautoCreatePR. - Use the narrowest runtime: local for developer-in-the-loop work, cloud for isolated async work, self-hosted for private network/data requirements.
- Give each subagent a bounded file or responsibility scope.
- Persist run metadata: runtime, repo URL, starting ref, run id, agent id, branch, PR URL, and linked ThumbGate evidence.
- Require verification output before merge, publish, deploy, or customer-facing claims.
Cursor SDK guardrails
- Attach ThumbGate MCP through the run environment so the agent can retrieve lessons and gates.
- Prefer a clean starting ref and a disposable branch for cloud VM runs.
- Do not set
autoCreatePRfor destructive, billing, release, or production tasks unless the gate check is clean. - If a cloud run finishes while the developer is offline, inspect the run transcript and PR diff before treating the result as accepted.
- Capture
thumbs_downfeedback when a run violates scope, skips proof, repeats a known mistake, or opens a noisy PR.
Output
For each governed run, report:
- Runtime: local, cloud, or self-hosted
- Scope: files, modules, or workflow the agent may touch
- Gates checked and result
- Verification evidence
- Branch or PR URL
- Any feedback captured for future prevention
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 · 43 lines · 30 tokens per session scan A b1f85b1b5529
programmatic-agent-runs is a skill published in the GitHub repository IgorGanapolsky/ThumbGate (26 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 456 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
agentguard
Runtime guardrails for AI coding agents. Stop loops, budget overruns, retry storms, and timeouts before they burn money. Zero dependencies, local-first, MIT licensed.
crm-pipeline-playbook
How to answer pipeline, renewal, and account-health questions using the CRM tools.
deciding-who-decides
Decides who holds authority for a change — the agent at the edge or a human gate — by matching decision rights to reversibility, evidence, and consequence, and names the escalation trigger. Use when an agent could act on something irreversible, trust-bearing, or thinly evidenced. Do not use for trivial reversible…
staying-on-mission
Tests the current work against a written, lasting mission anchor and forces one choice, re-anchor, escalate, or stop. Use when an agent keeps finishing tasks but the work drifts from the goal, scope creeps, the same action repeats in a loop, or standards slip one small step at a time. Do not use for a tiny edit with…
verifying-final-artifacts
Verifies the delivered artifact a consumer actually receives (a figure, chart, PDF, SVG, screenshot, compiled build, or deployed response) by regenerating it fresh and directly observing the output, not the source that produces it, and ends in one honest verdict. Use when the deliverable is a produced artifact and…
closing-stale-packets
Brings an abandoned or half-filled change packet to an honest terminal state by completing it, closing it with a recorded rationale, or deleting it. Use when ng status flags a scaffold or invalid packet, a long session left a draft behind, or work was abandoned mid-packet. Do not use for an actively in-progress…