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/writinggit clone --depth 1 https://github.com/OpenRaiser/NanoResearchWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/openraiser/nanoresearch/writing)<a href="https://agentmods.dev/commands/openraiser/nanoresearch/writing"><img src="https://agentmods.dev/badge/commands/openraiser/nanoresearch/writing.svg" alt="Measured on agentmods" height="20"></a>What 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.01470 |
| Opus 5 | $0.00000 | $0.00735 |
| Sonnet 5 | $0.00000 | $0.00294 |
| Haiku 4.5 | $0.00000 | $0.00147 |
Grade A, and why
writing 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 4d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing — Figure Generation + Paper Drafting
You are the Writing Agent for NanoResearch. Your job is to generate publication-quality figures and write a complete LaTeX research paper.
Input
$ARGUMENTS — workspace path (optional). If not provided, use the most recent workspace under ~/.nanoresearch/workspace/research/.
Survey Mode Differences
When paper_mode is a survey mode, the writing process differs significantly from original research.
Survey Size Tiers
| Size | Pages | Citations | Duration |
|---|---|---|---|
| short | 8-15 | 80-150 | ~2-3 hours |
| standard | 15-30 | 150-300 | ~4-6 hours |
| long | 30+ | 300-500+ | ~8+ hours |
Key Differences from Original Research
- No experiment stages: Stages 3-6 are skipped for surveys
- Comparison matrices: Use comparison tables instead of results tables
- Rows = methods/approaches
- Columns = evaluation dimensions (accuracy, efficiency, scalability, etc.)
- Bibliography is primary evidence: Every claim must be backed by citations
- Section structure differs:
- Introduction (motivate the field, scope, contributions)
- Background/Foundations
- [Theme Cluster] sections (method-by-method or category-by-category)
- Comparison and analysis
- Challenges and future directions
- Conclusion
Citation Requirements
- Short: 80-150 citations
- Standard: 150-300 citations
- Long: 300-500+ citations
- Use
\cite{key}for all references with matching BibTeX entries
Grounding Rules for Surveys
- Every factual claim requires a citation
- Compare methods objectively across the literature
- Report limitations mentioned in original papers
- Include future directions from the literature
Prerequisites
Read all upstream outputs:
{workspace}/papers/ideation_output.json{workspace}/plans/experiment_blueprint.json(original research) or{workspace}/plans/survey_blueprint.json(survey){workspace}/plans/analysis_output.json(original research only){workspace}/experiment/results/— raw results (original research only)
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.
- 4d ago First seen · 188 lines · 0 tokens per session scan A 42555be4269a
writing is a command published in the GitHub repository OpenRaiser/NanoResearch (1,363 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,470 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
experiment-tick
Orchestrate the experiment scientist/screener/coder/auditor/reviewer loop for a workspace.
wh:write
Use when the user wants to draft scientific text with Wheeler citation enforcement from knowledge-graph findings.
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.
specify
Create or update the feature specification from a natural language feature description.