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/openraiser/nanoresearch/statusgit clone --depth 1 https://github.com/OpenRaiser/NanoResearchWhat 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.00000 | $0.00544 |
| Opus 5 | $0.00000 | $0.00272 |
| Sonnet 5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
status 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 3d 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
Status — Check Research Pipeline Status
Show the current status of a NanoResearch workspace.
Instructions
-
Find the most recent workspace under
~/.nanoresearch/workspace/research/. If$ARGUMENTSis provided, treat it as a workspace path. -
Read
manifest.jsonfrom the workspace directory. -
Normalize the schema before display (manifests come in two variants):
- Old schema (
schema_version: "1.1"): stage keys are UPPERCASE (IDEATION,PLANNING...),current_stageis UPPERCASE (DONE,FAILED...), may have extra stages (INIT,FORMAT_FIX), artifacts are[{name, path, stage, checksum}] - New schema: stage keys are lowercase, artifacts are
["path"] - Always display in lowercase. Convert stage keys and
current_stageto lowercase. - The canonical stage order is:
ideation,planning,setup,coding,execution,analysis,figure_gen,writing,review. Skip any stages not in this list (e.g.,INIT,FORMAT_FIX). - For artifacts: if an entry is an object, use its
pathfield; if a string, use it directly.
- Old schema (
-
Display a summary table:
- Session ID
- Topic
- Schema version (old v1.1 / new)
- Current stage
- For each canonical stage: status (pending/running/completed/failed), timestamps
- List of produced artifacts with file paths
-
If no workspace exists, say so and suggest running
/project:research "topic"to start.
Output Format
Session: {session_id}
Topic: {topic}
Schema: {v1.1 | claude-code}
Current Stage: {current_stage}
Stage Status Started Completed
───── ────── ─────── ─────────
ideation completed 2026-03-18 10:00:00 2026-03-18 10:05:00
planning completed 2026-03-18 10:05:01 2026-03-18 10:10:00
setup running 2026-03-18 10:10:01 -
...
Artifacts:
- papers/ideation_output.json (12.3 KB)
- plans/experiment_blueprint.json (8.1 KB)
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.
- 3d ago First seen · 47 lines · 0 tokens per session scan A c3b1271761a1
status is a command published in the GitHub repository OpenRaiser/NanoResearch (1,361 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 544 tokens. 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
potpie-record
Record durable Potpie learnings after useful work.
potpie-feature
Use Potpie context before feature work. Load potpie-project-preferences first, and load potpie-infra-architecture when the change touches services, deployment, adapters, or runtime behavior.
agent
Agent hub - create, manage, and invoke specialized agents.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.