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 commands/jpantsjoha/ai-native-developer-experience/initgit clone --depth 1 https://github.com/jpantsjoha/ai-native-developer-experienceWhat 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.00016 | $0.00505 |
| Opus 5 | $0.00008 | $0.00253 |
| Sonnet 5 | $0.00003 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
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 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.
What it actually says
Initialise the project's delivery-planning records and human side of the harness. Skills supply capability; named humans supply authority.
- Run
/join-the-team:bootstrapfirst, including its dry-run. This is safe for an existing adoption: matching operating files are unchanged, existing project planning records are preserved, and missing vision/workflow/roadmap/status/changelog files are seeded. Stop on a reported operating-contract or adapter conflict. - If the repo already has code, run the read-only inspection pass to pre-fill what
the repository reveals instead of presenting a blank form:
python3 .agents/skills/operating-model-bootstrap/scripts/inspect_repo.py .Transcribe each finding into the profile as itsinferred — source: …; confirm: …marker, then confirm them one at a time with the accountable human. Never promote an inferred value to a verified fact without confirmation; the profile cannot goactivewhile any inferred field remains. - Ground the vision and delivery workflow from verified project evidence. Leave roadmap outcomes and status claims unpopulated until the Product Owner validates them; never turn template placeholders into invented progress.
- Ask the user for each team member, one at a time:
- name or handle;
- role — offer the standard set: accountable operator, product owner, data owner, integration owner, domain reviewer, governance/docs reviewer;
- accountable scope (e.g. which data domain, which requirements area);
- escalation channel (GitHub @mention, chat handle, or other).
- Fill the profile's Team roster and escalation table with the answers. Keep any
unfilled seat as an explicit
not yet established — owner: <role>; required before: <trigger>placeholder — never invent a person or a scope. - Reconcile the profile's Authority and approval roles table and escalation path with the roster so the two agree.
- Run
/join-the-team:validateand report the result. - Remind the user: roster seats are humans, not agents; an agent may route a question to a seat but can never hold one. Insufficient evidence = lane stops and the seat is tagged; silence never converts to permission.
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 · 37 lines · 16 tokens per session scan A af66cecb21c7
init is a command published in the GitHub repository jpantsjoha/ai-native-developer-experience (11 stars, last pushed 25d ago), licensed Apache-2.0. It adds 16 tokens to every session and 505 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-08-30.
Other commands, from other repositories
iteration-loop
Autonomous full iteration loop for cloud agents — Phase 1 (code-first auto direction lock + compass/plans + Review & Edit chain) through Phase 2–5 (execute → close → PR → merge-ready). Optional args: direction, scale (S|M|L|XL, default M). Not Done until Phase 5 exit checklist passes. Minimal human intervention; no…
iteration-drive
Drive the active iteration to completion — Phase 2 Autonomous Execute, Phase 3 iteration-close, Phase 4 Create PR, Phase 5 PR merge-ready loop (prefer babysit/-babysit; optional greploop when repo has it; else CI fallback) until mergeable. Not Done until Phase 5 exit checklist passes.
statuswt
You are checking the status of all active worktree task files in the project.
incident-action
Add or resolve action items on an incident. Provided by the Incident Review methodology.
migrate-tasks
Classify existing decompose tasks against a new seed version. Outputs task-migration-plan.yaml with categories (unchanged/modified/deprecated/added). Provided by the Living Spec methodology.
shapeup
Pitch 작성부터 Betting Table, 사이클 Hill Chart까지 Shape Up 워크플로우를 관리합니다.