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/zfinix/aster/background-processesnpx skills add Zfinix/aster --skill background-processesgit clone --depth 1 https://github.com/Zfinix/asterWhat 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.00041 | $0.00377 |
| Opus 5 | $0.00020 | $0.00188 |
| Sonnet 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 2d 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.
- 2d ago First seen · 26 lines · 41 tokens per session scan A dd4f85a7a660
background-processes is a skill published in the GitHub repository Zfinix/aster (40 stars, last pushed 7d ago), licensed Apache-2.0. It adds 41 tokens to every session and 377 once invoked, about $0.0002 per session on Opus 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
new-plugin
Factory line for adding a new HAR verification plugin (like playwright or rocketsim) for any framework — research the framework docs, build the template under src/templates/plugins/, register it everywhere, validate on a real repository, and open a PR. Use when asked to add/create a plugin, plugin template, or…
factory-line
Factory line for executing one station of a declared multi-station program — read the installed line bundle (har line status), plan parallel work into isolated HAR slots, run the cumulative gate with har line gate, and hand off for human review. Use when asked to "run a factory line", "run the next station", "execute…
v1-milestone
Factory line for executing one milestone of the HAR v1.0.0 refactor (epic os-factory/har#225) — plan the wave of parallel subagents, implement each issue in its own HAR slot, ship stacked PRs, run the fixture-e2e milestone gate, and hand off for review. Use when asked to "run the next v1 milestone", "work on v1.0.0"…
lemma-user
Operate an existing Lemma pod from the CLI as a human or agent: inspect resources, query tables and records under RLS, search and read pod files (converted markdown, page images), run functions and workflows, submit waiting workflow forms, chat with pod agents, run first-party tools, and execute third-party connector…
lemma-app-qa
Test and verify Lemma pod apps through real end-to-end user journeys in authenticated local and deployed contexts. Use when asked to QA, dogfood, smoke-test, regression-test, acceptance-test, reproduce, or verify a Lemma app; validate UI behavior against durable pod state; check auth, RLS, delegated workloads…
lemma-builder
Design and build complete Lemma pods: model tables/files/functions/agents/workflows/schedules/connectors/surfaces/apps from a problem statement, author a local pod bundle, import progressively with the Lemma CLI, and verify every layer. Use for pod design, creation, restructuring, import/export, and app development.…