Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add IgorGanapolsky/ThumbGate/plugin install 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/applyops-deploy)<a href="https://agentmods.dev/skills/igorganapolsky/thumbgate/applyops-deploy"><img src="https://agentmods.dev/badge/skills/igorganapolsky/thumbgate/applyops-deploy.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.1 | $0.00000 | $0.01362 |
| Opus 5 | $0.00000 | $0.00681 |
| Sonnet 5 | $0.00000 | $0.00272 |
| Haiku 4.5 | $0.00000 | $0.00136 |
Grade A, and why
applyops-deploy 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 8d 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.
curl -sf https://igorganapolsky.github.io/applyops/ | grep -c 'ApplyOps' How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: ApplyOps Deploy
Repeatable skill for deploying ApplyOps pages to GitHub Pages with full analytics.
When to use
- After any ApplyOps page edit (pricing, copy, new tier)
- After rotating analytics keys
- When CEO says "ApplyOps is down" or pages return 404
Architecture
- Source of truth:
IgorGanapolsky/Resumerepo,docs/applyops/(private) - Deployed to:
IgorGanapolsky/IgorGanapolsky.github.iorepo,/applyops/(public) - The Resume repo is private — GitHub Pages cannot serve from it. All public pages live in the
.github.iorepo.
Prerequisites
ghCLI authenticated- Analytics keys available in ThumbGate repo
.envor memory
Steps
1. Copy pages from Resume repo to public site repo
cd /Users/igorganapolsky/workspace/git/igor
# Clone if needed
[ -d IgorGanapolsky.github.io ] || git clone https://github.com/IgorGanapolsky/IgorGanapolsky.github.io.git
# Sync pages
cp Resume/docs/applyops/*.html IgorGanapolsky.github.io/applyops/
2. Inject analytics into all HTML pages
Every ApplyOps HTML file must have these three providers before </head>:
Plausible (tagged-events for custom event names):
<script defer data-domain="igorganapolsky.github.io" src="https://plausible.io/js/script.tagged-events.js"></script>
<script>window.plausible=window.plausible||function(){(window.plausible.q=window.plausible.q||[]).push(arguments)};</script>
GA4:
<script async src="https://www.googletagmanager.com/gtag/js?id=G-SZR5039QN4"></script>
<script>window.dataLayer=window.dataLayer||[];function gtag(){dataLayer.push(arguments)}gtag("js",new Date());gtag("config","G-SZR5039QN4");</script>
PostHog:
<script>!function(t,e){...posthog snippet...}(document,window.posthog||[]);posthog.init("$POSTHOG_API_KEY",{api_host:"https://us.i.posthog.com"})</script>
Get the PostHog project API key from
.env(POSTHOG_API_KEY) or the PostHog dashboard.
3. Add CTA click tracking
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.
- 8d ago First seen · 121 lines · 0 tokens per session scan A 2afaf21efa76
applyops-deploy is a skill published in the GitHub repository IgorGanapolsky/ThumbGate (26 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,362 tokens. 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-30.
Other skills, from other repositories
azure-sweep
Runs the full 8-layer Azure governance sweep using the Azure Sweeper agent.
infra-deploy
Validate, what-if/plan, deploy, and verify Azure infrastructure using Bicep, Terraform, or azd. Use when deploying a completed infrastructure phase to an environment.
staging-deploy
Build, push, migrate, and deploy to staging environment with health check verification. Use when deploying a completed phase to staging.
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.
runpod
Cloud GPU processing via RunPod serverless. Use when setting up RunPod endpoints, deploying Docker images, managing GPU resources, troubleshooting endpoint issues, or understanding costs. Covers all 5 toolkit images (qwen-edit, realesrgan, propainter, sadtalker, qwen3-tts).
project-tooling
Standard CLI tools for project infrastructure management.