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 leopu00/job-hunter-team --skill cloud-push-quarantinegit clone --depth 1 https://github.com/leopu00/job-hunter-teamWrote 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/leopu00/job-hunter-team/cloud-push-quarantine)<a href="https://agentmods.dev/skills/leopu00/job-hunter-team/cloud-push-quarantine"><img src="https://agentmods.dev/badge/skills/leopu00/job-hunter-team/cloud-push-quarantine/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/leopu00/job-hunter-team/cloud-push-quarantine"><img src="https://agentmods.dev/badge/skills/leopu00/job-hunter-team/cloud-push-quarantine.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.00033 | $0.00296 |
| Opus 5 | $0.00016 | $0.00148 |
| Sonnet 5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
cloud-push-quarantine 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 12d 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
cloud-push-quarantine — inspect, retry, resolve
The push keeps valid data moving and stores only privacy-safe metadata for a rejected row: table/type, opaque identity, sanitized reason, attempts and timestamps. Never ask for or print the source row.
- Inspect with
jht cloud quarantine list. Report only count, table, opaque identity, reason code, attempts and timestamps. - Fix the local cause through the owning workflow. Do not edit
jobs.dbby hand and do not special-case a table or error code. - Retry with
jht cloud quarantine retry <opaque-id>. This uses the canonical cloud writer. Read the result, then list again: success meansresolved. - Use
jht cloud quarantine resolve <opaque-id> --confirmonly when you have verified that the local row was intentionally removed or superseded and no retry is required. Resolution keeps the audit history.
retry all is allowed only after one shared cause was fixed and every listed
table was checked. Never copy message bodies, titles, paths, user IDs, server
details or credentials into chat, logs or the logbook.
What ships with it
6 files 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.
- 12d ago First seen · 26 lines · 33 tokens per session scan A 2d47cb971eab
cloud-push-quarantine is a skill published in the GitHub repository leopu00/job-hunter-team (49 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 296 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
atmos-auth
Authentication and identity management: providers (SSO/SAML/OIDC/GCP/Atmos Pro), identities, keyring, identity chaining, login/exec/shell/console, and github/sts for private GitHub access.
atmos-migration
This skill helps you migrate a repository to Atmos. It covers native Terraform, Terraform Workspaces, Terramate, Terragrunt, Makefiles, Justfiles, and Taskfiles. It gives minimum-disruption paths, file-layout options, workspace mapping, task-to-command mapping, generatehcl/script decomposition, and the remote-state…
atmos-stores
Store backends: AWS SSM, AWS Secrets Manager, Azure Key Vault, Google Secret Manager, Redis, Artifactory configuration, hooks integration, cross-component data sharing, atmos store CLI CRUD, type: store workflow step.
atmos-terraform
Terraform and OpenTofu orchestration: plan/apply/deploy, workspace management, backend config, varfile generation, authentication, binary selection (terraform/tofu), mixed-binary setups.
atmos-toolchain
Toolchain management: declarative dependencies, automatic installs, install/exec/search/env commands, Aqua registry integration, version pinning, package verification.
atmos-vendoring
Component vendoring: vendor.yaml and component.yaml manifests, immutable vendor.lock.yaml receipts, pulling from Git/S3/HTTP/OCI/Terraform Registry, --stack/--labels/--tags selector composition, native vendor update, clean, diff, config, and reviewed local component copies.