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/setup-generatenpx skills add jmagly/aiwg --skill setup-generategit 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/setup-generate)<a href="https://agentmods.dev/skills/jmagly/aiwg/setup-generate"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/setup-generate.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.00026 | $0.03973 |
| Opus 5 | $0.00013 | $0.01987 |
| Sonnet 5 | $0.00005 | $0.00795 |
| Haiku 4.5 | $0.00003 | $0.00397 |
Grade B, and why
setup-generate scanned grade B 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 5d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Expand the docker `install_hint` to mention `sudo usermod -aG docker $USER`. How it starts
The opening of the file, as written. The whole thing — 422 lines — stays where its author put it; the contents beside it link to each section on GitHub.
setup-generate
Generate a setup.manifest.yaml file for a project using the setup.aiwg.io/v1 SetupManifest language.
Trigger Phrases
- "generate a setup manifest for [project]"
- "create installer for [project]"
- "scaffold setup manifest"
- "write a setup.manifest.yaml for [directory]"
- "generate install workflow for [project]"
- "generate dev installer for [project]"
Parameters
project-dir (positional, optional)
Path to the project root. Defaults to ..
--output (optional)
Manifest path to create. Default: ./setup.manifest.yaml.
--name (optional)
Manifest metadata.name. Default: package name or project directory name.
--type (optional)
Install type: user, developer, or ci. Default: developer.
--platform (optional)
Target platform: linux, macos, windows, or docker.
--force (optional)
Overwrite existing generated manifest/script files.
--type (optional)
Install type to generate: user, developer, or ci.
Default: user.
user— production/end-user deployment (default, behavior unchanged from previous versions)developer— local development environment standup with OS configurationci— headless pipeline setup
When --type developer, output filename is setup.dev.manifest.yaml. When --type user, output is setup.user.manifest.yaml (or setup.manifest.yaml if no type is specified for backwards compatibility).
--interactive (optional)
Ask clarifying questions before generating.
Execution Flow
Phase 1: Discovery
- Read the project root to understand structure:
- Check for
package.json,requirements.txt,Cargo.toml,go.mod,Makefile, etc. - Check for
README.md,INSTALL.md,docs/install.md - Check for existing
setup.manifest.yaml
- Check for
- Parse local project cues when they are available; the CLI entrypoint emits a conservative starter manifest and leaves richer project-specific authoring to the agent skill.
- If
--interactive, ask:- What OSes must be supported?
- What are the hard prerequisites (git, node, python version)?
- Is there a config directory that needs to be created?
- Does the project chain sub-projects?
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.
- 5d ago First seen · 422 lines · 26 tokens per session scan B 21fbe1c8b8d2
setup-generate is a skill published in the GitHub repository jmagly/aiwg (208 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 3,973 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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.
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.
import-issues
Stage explicitly selected GitHub issues onto the drafting table as quoted source. Never searches, never writes back to GitHub, never installs gh.
stop
Issue a stop-work order — pause the shift immediately, leaving unfinished items open.
purge
Permanently delete this project's Nightshift state. Does not uninstall the plugin.