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/jmagly/aiwg/dev-mode-initnpx skills add jmagly/aiwg --skill dev-mode-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/dev-mode-init)<a href="https://agentmods.dev/skills/jmagly/aiwg/dev-mode-init"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/dev-mode-init.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.00033 | $0.01513 |
| Opus 5 | $0.00016 | $0.00757 |
| Sonnet 5 | $0.00007 | $0.00303 |
| Haiku 4.5 | $0.00003 | $0.00151 |
Grade A, and why
dev-mode-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 3d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Mode Init
You activate AIWG dev mode, rebuild the local source, deploy the developer toolkit, and run a dev health check. All operations go through the AIWG Steward agent and CLI — no direct file writes.
Triggers
- "switch to dev mode" → full dev mode bootstrap
- "aiwg use dev" → full dev mode bootstrap
- "activate dev mode" → full dev mode bootstrap
- "use local repo source" → switch CLI to dev + build
- "switch back to stable" → deactivate dev mode
- "rebuild and redeploy dev" → build + redeploy aiwg-dev without switching mode
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Full init | "switch to dev mode" | All steps |
| From repo path | "use dev mode at ~/dev/aiwg" | Switch + build from path |
| Stable | "switch back to stable" | aiwg --use-stable |
| Rebuild only | "rebuild dev" | Build + redeploy, skip mode switch |
| Check mode | "am I in dev mode?" | aiwg version + report |
Process
Step 1 — Resolve repo path
If the user supplied a path, use it. Otherwise default to the current working directory.
# Verify the target looks like the AIWG repo
ls package.json src/ agentic/ 2>/dev/null
If package.json is not found, stop and report: "Directory does not appear to be an AIWG repo — no package.json found."
Step 2 — Switch CLI to dev mode
aiwg --use-dev <resolved-path>
Expected output confirms: Switched to dev mode. Dev repo: <path>
If already in dev mode pointing at the same path, skip and note "already in dev mode".
Step 3 — Build local source
# TypeScript compile + web app build
npm run build
On failure: report the tsc or vite error, stop, and suggest running npm run build manually to see full output. Do not proceed past a broken build.
On success: note build time and output sizes (xterm, index bundles).
Step 4 — Deploy aiwg-dev addon (with Steward)
aiwg use aiwg-dev
This deploys:
- Steward agent (via aiwg-utils dependency)
- Dev rules (skill-placement, no-circular-skill-calls, component-completeness, addon-boundaries)
- Dev skills (dev-doctor, devkit-create-*, devkit-validate, devkit-test)
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.
- 3d ago First seen · 195 lines · 33 tokens per session scan A e8f99c10fa85
dev-mode-init is a skill published in the GitHub repository jmagly/aiwg (208 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 1,513 once invoked, about $0.0002 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 skills, from other repositories
hunt
Compose a guided or automatic shift from the ready catalog, then review it first or run it directly under one time budget. Use when the owner wants to choose jobs or let Nightshift find the highest-value applicable work.
archive
File the finished part of the run state into a dated archive — shipped items, research, opportunities, the rotated journal, and handled snags. The live files stay lean; the facts stay on disk.
doctor
Read-only Nightshift diagnosis — workspace, rules, markers, session, process lease, watchman, deadline, and classified next actions. Use when a shift looks wrong, recovery is unclear, or the owner asks what Nightshift sees. Never repairs by being invoked.
import-issues
Stage explicitly selected GitHub issues onto the drafting table as quoted source. Never searches, never writes back to GitHub, never installs gh.
purge
Permanently delete this project's Nightshift state. Does not uninstall the plugin.
stop
Issue a stop-work order — pause the shift immediately, leaving unfinished items open.