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 Zfinix/aster --skill background-processesgit clone --depth 1 https://github.com/Zfinix/asterWrote 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/zfinix/aster/background-processes)<a href="https://agentmods.dev/skills/zfinix/aster/background-processes"><img src="https://agentmods.dev/badge/skills/zfinix/aster/background-processes/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/zfinix/aster/background-processes"><img src="https://agentmods.dev/badge/skills/zfinix/aster/background-processes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 10 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00041 | $0.00377 |
| Opus 5.5 | $0.00016 | $0.00151 |
| Sonnet 5.5 | $0.00008 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
background-processes 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 1mo 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.
`for i in $(seq 1 40); do curl -s localhost:3000 >/dev/null && echo UP && break; sleep 0.5; done` What it actually says
Background processes
- Never run a server in the foreground of a tool call. It runs until the
timeout kills it and the round is wasted. Background it and detach:
bash -lc "nohup bun run dev > /tmp/dev.log 2>&1 & echo started". - Logs go to a file, not the pipe. A backgrounded process writing to the
pipe keeps the call alive. Redirect to
/tmp/<name>.log, then read the log withtail -20 /tmp/<name>.login a later call. - Wait by polling the port, never by sleeping.
for i in $(seq 1 40); do curl -s localhost:3000 >/dev/null && echo UP && break; sleep 0.5; done - Verify it actually started. After the poll, check the log tail for the
startup line or errors:
tail -5 /tmp/dev.log. A backgrounded crash looks identical to success until you look. - Kill by pattern when done or when restarting.
pkill -f "bun run dev" || truebefore starting a second instance; two servers on one port is a classic wasted hour. - One-shot beats long-lived when possible. Prefer
bun run buildplus a static check over starting a dev server, andcargo testovercargo watch. Reach for a background server only when the task needs a live process.
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.
- 1mo ago First seen · 26 lines · 41 tokens per session scan A dd4f85a7a660
background-processes is a skill published in the GitHub repository Zfinix/aster (129 stars, last pushed 8d ago), licensed Apache-2.0. It adds 41 tokens to every session and 377 once invoked, about $0.0002 per session on Opus 5.5. 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
harness
Use when governing a workspace's control plane, code or not — the 01-TOOLS/ tooling layer, the 02-DOCS/ chaos→knowledge wiki, the root Knowledge map. Audits it, migrates legacy XX- folders, scaffolds provider tooling, sweeps the inbox, eats a file the person hands over ("cómete este fichero", "guárdalo en la…
office-xlsx
Read, create, and modify Excel workbooks (.xlsx), including data, formulas, formatting, and pandas analysis. Use for Excel inputs or deliverables. Load before running Office commands. Data and formula tasks skip visual inspection; inspect only for formatting or layout needs. Use only bundled LibreOffice unless the…
office-pptx
Create, read, edit, and check PowerPoint presentations (.pptx), including slide text, tables, images, and charts. Use when a PPTX file is an input or requested deliverable. Load this skill before running Office commands. Use only bundled LibreOffice unless the user explicitly opts out; without that opt-out, do not…
office-docx
Create, read, edit, and check Word documents (.docx), including reports, letters, and formatted tables. Use when a DOCX file is an input or requested deliverable. Load this skill before running Office commands. Use only bundled LibreOffice unless the user explicitly opts out; without that opt-out, do not search for…
ctx
Codebase intelligence and evidence-driven governance with the indexed ctx CLI. Use when exploring an unfamiliar repository, locating symbols or callers, checking for existing implementations, estimating change impact, enforcing architecture rules, scoring a branch, finding hotspots or duplication, or analyzing…
author-and-promote-skill
Use when you've drafted or improved a skill locally and want to publish it to a shared pack — walks through validating the draft, finding the target pack, running the promote script, and reviewing the staged diff before it ships.