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.
git clone --depth 1 https://github.com/TobiasBlask/open-paper-machineWrote 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/tobiasblask/open-paper-machine/triage-project)<a href="https://agentmods.dev/commands/tobiasblask/open-paper-machine/triage-project"><img src="https://agentmods.dev/badge/commands/tobiasblask/open-paper-machine/triage-project.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.1 | $0.00062 | $0.00413 |
| Opus 5 | $0.00031 | $0.00206 |
| Sonnet 5 | $0.00012 | $0.00083 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade A, and why
triage-project 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 8d 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
/triage-project — Should You Continue This Project?
Read agents/research-strategist.md and execute Mode 1: Project Triage.
The user describes their current research project and its state. Evaluate using 5 signals:
| Signal | Continue | Pivot | Kill |
|---|---|---|---|
| Results | Core hypothesis validated | Interesting side results | Core assumption disproven |
| Competition | Still ahead or unique angle | Others approaching differently | Scooped on main contribution |
| Impact | Conclusion-first test passes | Original framing weak, results support different framing | Can't write compelling conclusion |
| Effort remaining | Manageable, clear path | Moderate, toward a different goal | Large, success still uncertain |
| Motivation | Engaged, believes in the work | Curious about pivot direction | Dreading the work |
Deliver a clear Continue / Pivot / Kill verdict with reasoning.
- For Pivot: suggest a concrete new framing — not just "consider pivoting."
- For Kill: suggest what to salvage (workshop paper, blog post, dataset release).
Always flag the sunk cost fallacy explicitly. Respect the work done, then recommend based on forward-looking expected value only.
$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.
- 8d ago First seen · 43 lines · 62 tokens per session scan A f4de057abd67
triage-project is a command published in the GitHub repository TobiasBlask/open-paper-machine (18 stars, last pushed 5mo ago), licensed MIT. It adds 62 tokens to every session and 413 once invoked, about $0.0003 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
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
genshijin-compress
A command for safely shortening Markdown or text files into the genshijin style.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.
nyann:diff-profile
Compare two nyann profiles side-by-side and show what changes between them: hooks, branching, CI, documentation, extras, governance. Useful before switching profiles to understand the impact.
summary
Generate a consolidated project brief from design artifacts. For the full spec package with YAML specs and validation, use /compile instead.
spec
Generate technical specifications from design artifacts.