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/muzafferkadir/nextjs-loop-engineering-starter/source-command-loop-startnpx skills add muzafferkadir/nextjs-loop-engineering-starter --skill source-command-loop-startgit clone --depth 1 https://github.com/muzafferkadir/nextjs-loop-engineering-starterWhat 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.00024 | $0.00478 |
| Opus 5 | $0.00012 | $0.00239 |
| Sonnet 5 | $0.00005 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
source-command-loop-start 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
source-command-loop-start
Use this skill when the user asks to run the migrated source command loop-start.
Command Template
Read the following files in order:
- AGENTS.md — project context, stack, rules
- LOOP.md — loop lifecycle, limits, denylist
- STATE.md — current state (if it says
loop: paused, STOP immediately) - BACKLOG.md — feature backlog
Then based on the argument:
If the argument is "report" or empty: Run the $loop-report skill:
- Check open PRs, CI status, BACKLOG.md
- Update STATE.md (High Priority, Watch List, Resolved)
- Append to loop-run-log.md
- DO NOT write code
- Commit the state update: ask first if a human is present in this session; if this is an unattended scheduled run, commit and push directly to main and report the change — no PR needed for loop memory
If the argument starts with "plan": Run the $loop-plan skill with the rest of the argument as the idea (or the top BACKLOG.md ## Ideas item if no idea is given):
- Check precedent (BACKLOG-DONE.md, loop-run-log.md, git log)
- Fits one run → spec it into the Backlog
- Too broad → propose a split and ASK THE HUMAN — never spec silently
- DO NOT write code
If the argument is "build": Run the $loop-build skill:
- Sync main:
git checkout main && git pull --ff-only— dirty tree or failed pull → report in STATE.md and STOP - Check the lock:
bash scripts/loop-lock.sh status - If free: acquire the lock, pick the highest-priority Backlog item
- Implement all acceptance criteria with tests
- Visually inspect UI changes with the $ui-verify skill
- Run the verifier:
bash scripts/run-verifier.sh— must APPROVE - Open a PR per the git protocol in AGENTS.md
- Release the lock
Always run bash scripts/budget-check.sh at the start and end.
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 · 51 lines · 24 tokens per session scan A 9fda27afbf44
source-command-loop-start is a skill published in the GitHub repository muzafferkadir/nextjs-loop-engineering-starter (10 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 478 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-31.
Other skills, from other repositories
claude-loop
Autonomous orchestrated loop that works through a prd.json story-by-story using a fresh Task subagent per story. Use this skill whenever the user asks to "run the loop", "claude loop", "start the loop", "kick off the loop", "work through the prd", "process prd.json", "implement all the stories", "iterate through the…
deliver
Drive a whole phase or feature-set to "merged + Done" — themed batching over /drive, front-loaded architectural questions, phase-gate ceremonies, and lossless resume. The long-horizon recipe ABOVE /drive; pair with native /goal " delivered" for hands-off, multi-turn completion.
drive
Drive one tracker ticket end-to-end — claim, plan, implement, verify, cross-review, and ship — autonomously, pausing only for architectural decisions. The per-ticket recipe; pair with native /goal " is merged" for unattended multi-turn completion.
forge-orchestrate
Per-round dispatch loop for forge's orchestrator. Lists ready tasks, asks user to approve, then claims, dispatches, and spawns worker subagents via the host's Task tool. Polls open questions and surfaces them for user answers. Suggest-don't-force — no automatic claim, no internal long-polling.
update-spec
Draft an ephemeral ADR for an in-flight architectural decision (--draft), then propagate the accepted decision to SPEC + PRD + phases.yaml + tracker bodies atomically (--apply ) via the apply-decision verb's resumable journal.
autopilot
Take a product idea from the discovery interview all the way to a running delivery loop — drive the spec chain (BRIEF → PRD → SPEC → CONTEXT → phases.yaml → tracker), pausing ONLY at the human approval gates, then roll into /deliver. The single front door for a new forge product; pair with native /goal for hands-off…