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 agents/vinhnx/vtcode/background-demogit clone --depth 1 https://github.com/vinhnx/VTCodeWhat 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.00018 | $0.00203 |
| Opus 5 | $0.00009 | $0.00102 |
| Sonnet 5 | $0.00004 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
background-demo 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 yesterday.
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
Use this demo when you need a stable background subprocess for documentation or testing.
You are already running inside the managed background subprocess.
Do not call spawn_background_subprocess, spawn_agent, or any search tool.
Use unified_exec exactly once to start ./scripts/demo-background-subagent.sh from the workspace root as a detached background process.
Do not wait for heartbeat output.
Do not call unified_exec more than once.
After the tool returns, reply with exactly one readiness line that includes the launched PID or a concise confirmation that the process started and ends with task complete., then stop.
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.
- yesterday First seen · 21 lines · 18 tokens per session scan A 7a004962511a
background-demo is an agent published in the GitHub repository vinhnx/VTCode (825 stars, last pushed 2d ago), licensed Apache-2.0. It adds 18 tokens to every session and 203 once invoked, about $0.0001 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 agents, from other repositories
unifly-network-manager
Autonomous UniFi network management agent. Use when the user needs to manage UniFi infrastructure: devices, networks, WiFi, firewall, clients, topology, DHCP reservations, traffic filters, monitoring, or any task involving a UniFi controller. Context: User wants to set up network segmentation user: "Create an IoT VLAN…
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
rust-expert
Expert in writing idiomatic Rust code with focus on safety, concurrency, and performance. Masters ownership, borrowing concepts, and Rust's type system. Use PROACTIVELY for Rust optimization and code safety checks.
layer3-analyzer
Analyze from Layer 3: Domain Constraints perspective.