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/devkit-create-frameworknpx skills add jmagly/aiwg --skill devkit-create-frameworkgit clone --depth 1 https://github.com/jmagly/aiwgWhat 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.00009 | $0.01065 |
| Opus 5 | $0.00005 | $0.00532 |
| Sonnet 5 | $0.00002 | $0.00213 |
| Haiku 4.5 | $0.00001 | $0.00106 |
Grade A, and why
devkit-create-framework 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 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.
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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create AIWG Framework
Create a new AIWG framework with complete lifecycle structure.
Process
1. Validate Framework Name
Check that $ARGUMENTS contains a valid framework name:
- Must be kebab-case (lowercase with hyphens)
- Must not conflict with existing frameworks
Check existing frameworks:
ls ~/.local/share/ai-writing-guide/agentic/code/frameworks/
2. Interactive Design (if --interactive)
If --interactive is specified, guide the user through framework design:
Framework Purpose:
What lifecycle does this framework manage? (e.g., software development, marketing campaigns, legal cases)
Target Audience:
Who will use this framework? (e.g., development teams, marketing departments, legal firms)
Phase Structure:
What phases does this lifecycle include? Default: inception, elaboration, construction, transition Custom examples: discovery, analysis, synthesis, publication
Agent Categories:
What types of roles are needed?
- Analysis roles (analysts, researchers)
- Design roles (architects, designers)
- Implementation roles (developers, writers)
- Quality roles (reviewers, testers)
- Management roles (coordinators, managers)
Template Categories:
What artifact types will be produced?
- Planning documents
- Requirements documents
- Design documents
- Implementation artifacts
- Quality artifacts
- Deployment artifacts
3. Execute Scaffolding
Run the CLI scaffolding tool:
node ~/.local/share/ai-writing-guide/tools/scaffolding/scaffold-framework.mjs \
<name> \
--description "<derived from interactive>" \
--phases "<phase1,phase2,...>"
4. Post-Creation Guidance
After scaffolding, provide guidance on next steps:
Immediate Actions:
- Review and customize
actors-and-templates.md - Define your first agents for each phase
- Create initial templates for key artifacts
Agent Creation Priority:
- Phase 1: Create 2-3 core agents per phase
- Phase 2: Add specialized agents as needed
- Phase 3: Add orchestration agents for workflows
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 · 146 lines · 9 tokens per session scan A 5ae45d375132
devkit-create-framework is a skill published in the GitHub repository jmagly/aiwg (205 stars, last pushed 4d ago), licensed MIT. It adds 9 tokens to every session and 1,065 once invoked, about $0.0000 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
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.
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.
reset
Abandon current Nightshift runtime mechanics without deleting the owner's work or evidence.