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 jmagly/aiwg --skill daemon-initgit clone --depth 1 https://github.com/jmagly/aiwgWrote 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/jmagly/aiwg/daemon-init)<a href="https://agentmods.dev/skills/jmagly/aiwg/daemon-init"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/daemon-init/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/jmagly/aiwg/daemon-init"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/daemon-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Rogue Agent · line 61 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00017 | $0.01173 |
| Opus 5 | $0.00009 | $0.00587 |
| Sonnet 5 | $0.00003 | $0.00235 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
daemon-init 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 9d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daemon Init
You initialize AIWG daemon mode configuration from a named profile. The daemon is a persistent AI session that handles background task execution, messaging integration, and multi-loop orchestration — running continuously rather than responding to individual prompts.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "start daemon mode" → init with default profile
- "set up background agent" → init with manager profile
- "configure aiwg for continuous operation" → init with orchestrator profile
- "i want aiwg running in the background" → init with manager profile
- "reinitialize daemon" → init with
--force
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Default init | "initialize daemon" | Run aiwg daemon-init |
| Named profile | "init daemon as orchestrator" | Run aiwg daemon-init orchestrator |
| Force reinit | "reinitialize daemon config" | Run aiwg daemon-init --force |
| Worker mode | "set up a worker daemon" | Run aiwg daemon-init worker |
| Monitor mode | "run daemon in monitoring mode" | Run aiwg daemon-init monitor |
Behavior
When triggered:
-
Extract intent:
- Is a profile name specified? Default to
managerif not. - Is
--forceneeded (user mentioned reinitializing or overwriting)?
- Is a profile name specified? Default to
-
Select the appropriate profile:
Profile Authority Use Case manager(default)Balanced — orchestrate and execute General-purpose persistent agent orchestratorHigh — coordinate other agents Driving multi-agent workflows workerLow — execute, minimal decisions Background task execution monitorRead-only — observe and alert Ops monitoring, health checks -
Run the command:
# Default profile (manager) aiwg daemon-init # Named profile aiwg daemon-init orchestrator aiwg daemon-init worker aiwg daemon-init monitor # Overwrite existing config aiwg daemon-init --force aiwg daemon-init orchestrator --force
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.
- 9d ago First seen · 148 lines · 17 tokens per session scan A 67bad85c3e19
daemon-init is a skill published in the GitHub repository jmagly/aiwg (211 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 1,173 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-09-03.
Other skills, from other repositories
surge
Use when a user provides a PRD, spec, or detailed requirements document and needs a full project delivered through iterative expert orchestration — multi-round analyze/research/design/implement/QA cycles with convergence detection. NOT for: single-file edits, quick prototypes, simple Q&A, or tasks without a written…
goal-writer
Drafts a goal+rider document pair that briefs an autonomous coding agent on one round of work — a goal file under 4,000 characters (sized to fit the /goal command in both Claude Code and Codex) plus an unbounded rider with phased plans and named depth tests. Use when the user says "draft a goal", "write a goal+rider"…
horizon
Run a durable Horizon workflow for a multi-feature goal with bounded autonomous retries and an audit trail.
check-in
Record a Parallax protocol checkpoint with concrete evidence before gated implementation work.
debug
Perform an evidence-based Parallax diagnosis or post-build audit and verify the repair.
hyperplan
Harden a non-trivial plan through a three-round adversarial critique and evidence-based synthesis.