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/colemurray/background-agents/onboardingnpx skills add ColeMurray/background-agents --skill onboardinggit clone --depth 1 https://github.com/ColeMurray/background-agentsWrote 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/colemurray/background-agents/onboarding)<a href="https://agentmods.dev/skills/colemurray/background-agents/onboarding"><img src="https://agentmods.dev/badge/skills/colemurray/background-agents/onboarding.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.00047 | $0.03441 |
| Opus 5 | $0.00023 | $0.01721 |
| Sonnet 5 | $0.00009 | $0.00688 |
| Haiku 4.5 | $0.00005 | $0.00344 |
Grade C, and why
onboarding scanned grade C with 2 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 4d 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
Hand off to user for each service. Use AskUserQuestion to collect credentials. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl https://open-inspect-control-plane-{deployment_name}.{subdomain}.workers.dev/health How it starts
The opening of the file, as written. The whole thing — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open-Inspect Deployment Guide
You are guiding the user through deploying their own instance of Open-Inspect. This is a multi-phase process requiring user interaction for credential collection and external service configuration.
Before Starting
Use TodoWrite to create a checklist tracking these phases:
- Initial setup questions
- Repository setup
- Credential collection (Cloudflare, Vercel, Modal, Anthropic)
- GitHub App creation (+ Google OAuth if enabled)
- Slack App creation (if enabled)
- Security secrets generation
- Terraform configuration
- Terraform deployment (two phases)
- Post-deployment Slack setup (if enabled)
- Post-deployment GitHub Bot setup (if enabled)
- Web app deployment
- Verification
- CI/CD setup (optional)
Phase 1: Initial Questions
First, generate a random suffix suggestion for the user:
echo "Suggested deployment name: $(openssl rand -hex 3)"
Use AskUserQuestion to gather:
- Directory location - Where to create the project (default: current directory or ~/workplace/open-inspect-{suffix})
- GitHub account - Which account/org hosts the private repo
- Deployment name - A globally unique identifier for URLs (e.g., their GitHub username, company
name, or the random suffix generated above). Explain this creates URLs like
open-inspect-{deployment_name}.vercel.appand must be unique across all Vercel users. - Slack integration - Yes or No
- GitHub bot integration - Yes or No (automated PR reviews and comment-triggered actions)
- Sign-in providers - GitHub, Google, or both. At least one is required.
- Prerequisites confirmation - Confirm they have accounts on Cloudflare, Vercel, Modal, Anthropic
Phase 2: Repository Setup
Execute these commands (substitute values from Phase 1):
mkdir -p {directory_path}
gh repo create {github_account}/open-inspect-{name} --private --description "Open-Inspect deployment"
cd {directory_path}
git clone [email protected]:ColeMurray/open-inspect.git .
git remote rename origin upstream
git remote add origin [email protected]:{github_account}/open-inspect-{name}.git
git push -u origin main
npm install
npm run build -w @open-inspect/shared
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.
- 4d ago First seen · 374 lines · 47 tokens per session scan C 11d6ef398a81
onboarding is a skill published in the GitHub repository ColeMurray/background-agents (2,712 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 3,441 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (harvests environment variables, 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
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
rule
Skill "rule" from x-cmd/x-cmd, covering rule — rules to rule, 核心命令, 规则文件格式, 示例 and 验证规则文件格式.
cve
Look up CVE records via x cve — cached, zero-API-key, daily xz TSV. Load for cve, vulnerability id, kev, epss, nvd, cvelist, or security advisory.
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.
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.
terraform-search-import
Discover existing cloud resources using Terraform Search queries and bulk import them into Terraform management. Use when bringing unmanaged infrastructure under Terraform control, auditing cloud resources, or migrating to IaC.