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/missingpackage/nightshift/research-loopgit clone --depth 1 https://github.com/MissingPackage/nightshiftWhat 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.00339 |
| Opus 5 | $0.00008 | $0.00169 |
| Sonnet 5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
research-loop 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 yesterday.
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
Continue the autonomous research loop for this project.
Follow the loop-iteration skill exactly. For this iteration:
- Re-anchor from disk: the PI directive files referenced in
research/AGENDA.md(orHANDOFF.md), then AGENDA §1 "next decidable", then the PI docket. - Execute the single next decidable research step. Standing constraints: pre-register the prediction in
research/predictions.mdBEFORE any--execute; dry-run and show cost estimates before real API spend; hard-stop and docket if projected spend exceeds the session budget in CLAUDE.md. - Before scheduling the next iteration, spawn the
loop-verifieragent with your claimed outcome. On FAIL: fix if decidable this iteration, otherwise docket and stop. - Grade the outcome against the pre-registered prediction — honestly. Negative and null results are recorded with the same care as positives ("failures are data").
- Update: journal (append), AGENDA §1 (refresh in place), docket (append PI-gated items).
- Send the digest: 3-6 lines — what was done, why, what the results say, what's next.
- Schedule the next iteration (self-paced) — or STOP BY DESIGN if all remaining work is PI-gated, stating the docket items that need rulings. Never invent scope to keep the loop alive.
State machine and escalation semantics: ORCHESTRATION.md §4; goal spine (multi-phase research goals): §1-2.
$ARGUMENTS
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.
- yesterday First seen · 20 lines · 16 tokens per session scan A a3683cb3f0a3
research-loop is a command published in the GitHub repository MissingPackage/nightshift (2 stars, last pushed 15d ago), licensed MIT. It adds 16 tokens to every session and 339 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 commands, from other repositories
research
Research a technical or product question.
safe-build
Build the application for development or production.
update
Use when: search results seem noisy, after bulk imports, or for periodic memory/registry maintenance.
plan-workflow
Generate a skill chain plan for a high-level goal by analyzing the skills registry for input/output compatibility.
music-suno-prompt
Grounded Suno prompt synthesis from local knowledge corpus + persona canon + label canon. No vibes-prompting.
lrn
Execute the /vibeguard:learn command. $ARGUMENTS.