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 WYRE-AI/msp-claude-plugins --skill jobsgit clone --depth 1 https://github.com/WYRE-AI/msp-claude-pluginsWrote 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/wyre-ai/msp-claude-plugins/jobs)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/jobs"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/jobs/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/wyre-ai/msp-claude-plugins/jobs"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/jobs.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.00042 | $0.01237 |
| Opus 5 | $0.00021 | $0.00619 |
| Sonnet 5 | $0.00008 | $0.00247 |
| Haiku 4.5 | $0.00004 | $0.00124 |
Grade A, and why
Axcient Jobs 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 7d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Axcient Jobs
Overview
A job is one configured backup task running against a device — the thing
that actually produces recovery points. Jobs always nest under a specific
client_id and device_id; there is no organization-wide job list. Get a
device's job IDs from axcient_get_device (the jobs array) or
axcient_list_devices_by_client first.
Tools
| Tool | Description | Arguments |
|---|---|---|
axcient_list_jobs_by_device |
All jobs for a device | client_id, device_id |
axcient_get_job |
One job's detail | client_id, device_id, job_id |
axcient_get_job_history |
Run history for a job | client_id, device_id, job_id, limit?, offset?, starttime_begin? |
There is no job-level list at the organization or client level — jobs are always reached through a specific device.
Job Types: BRC vs Replibit
The job schema is a tagged union — org_level_jobs_response is one of
org_level_brc_job or org_level_replibit_job, mirroring the device-level
product split (BRC vs X360RECOVER). Handle both shapes: a legacy
appliance's jobs return the BRC shape, current-generation appliances and
D2C devices return the Replibit shape. Don't assume one field set applies
to every job in a fleet with mixed appliance generations.
Job Thresholds
Jobs carry the same threshold structure as devices —
vault_rp_threshold, cloud_rp_threshold, local_rp_threshold,
protection_threshold — each an object with value, enabled, and
overridden. overridden: true means this job's threshold deviates from
the client- or organization-level default; check it before assuming a
device-level threshold applies uniformly across all its jobs.
Job History
axcient_get_job_history
Parameters:
client_id,device_id,job_id-- requiredlimit,offset-- pagination (groups of up to 1500)starttime_begin-- unix timestamp floor; only returns runs starting at or after this time
Known upstream caveat: community testing against Axcient's API found
this endpoint unreliable in some environments — treat an empty or
unexpected result here as worth double-checking against
axcient_get_device_restore_points (which reflects what actually landed,
regardless of what the history endpoint reports) before concluding a job
has never run.
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.
- 7d ago First seen · 124 lines · 42 tokens per session scan A b38f4c55b903
Axcient Jobs is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 8d ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,237 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-09-04.
Other skills, from other repositories
rented-server-setup
Runs an open model in the cloud two ways, and makes the user choose with real numbers. Route A is OVHcloud AI Endpoints, an EU-owned per-token API with zero idle cost, for spiky usage and EU jurisdiction. Route B rents one single-tenant RunPod GPU pod in a region the user picks, serving the model on vLLM behind a…
allow-team
Puts a running Open WebUI or Odysseus on a shareable public URL through an ngrok tunnel, so a teammate can sign in and use the local models without installing anything. Use when the user says "share Open WebUI with my team", "share Odysseus with my team", "let my colleague use my local AI", "expose Open WebUI", "share…
gcloud-cli-health-check
Run a Google Cloud CLI (gcloud) health check — verify installation, authentication, active project, recommended region, enabled APIs (run, cloudbuild, artifactregistry, secretmanager, cloudresourcemanager, iam, plus gmail/calendar/monitoring/logging), API access token, billing, IAM bindings, service accounts, and…
dell-idrac-bmc-ops
Bring a Dell PowerEdge BMC (iDRAC) onto the network headlessly, standardize its baseline settings, stage its firmware, and drive an unattended Proxmox/Linux install through it — including generation-specific Redfish/racadm gotchas, the identity-before-power-action rule, and the phantom-drive failure mode caused by…
terrakube-ops
Operate self-hosted Terrakube (remote OpenTofu/Terraform plan/apply, state, and workspace locking) — the canonical login/plan/apply workflow, why a targeted apply is dangerous, workspace lock recovery, the offline-mirror gotcha, and the token-rotation trap. Use when running or observing a Terrakube plan/apply…
openbao-dynamic-aws-creds
Replace a static AWS access key on a workstation or CI runner with short-lived STS credentials minted on demand by OpenBao's (or Vault's) AWS secrets engine, via an AWS credentialprocess wrapper. Covers the architecture, bring-up order, verification, plugin-upgrade caution, and common failure modes. Use when a…