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/endorhq/rover/create-issuegit clone --depth 1 https://github.com/endorhq/roverWhat 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.01582 |
| Opus 5 | $0.00000 | $0.00791 |
| Sonnet 5 | $0.00000 | $0.00316 |
| Haiku 4.5 | $0.00000 | $0.00158 |
Grade A, and why
create-issue 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a new GitHub issue
Create a new GitHub issue in the current repository. This command is a process, so you must go through all the steps and wait for user input when required. You can clearly identify when you must wait for user input based on the template. This is very important.
This command has three phases:
- Get user requirements and task description
- Identify the task context
- Create the issue
You must complete the three phases in order.
Phase: Get user requirements and task description
-
Ask the user to briefly describe the task they want to accomplish.
-
Based on the user input and your current understanding of the project (from Claude.md and any other file you consider), provide an expanded and more complete 1–2 paragraphs about the scope and the end goal of the task. Max 250 characters.
update the website dark palette to use cyan as the base color instead of green.
Expanded task description:
Update the website’s dark color palette by switching the base color from green (previously defined in app.css) to cyan. Make sure the updated palette maintains enough contrast to comply with accessibility standards.
update the website dark palette to use cyan as the base color instead of green.
Expanded task description:
Update the website palette to cyan.
update the website dark palette to use cyan as the base color instead of green.
Expanded task description:
The goal of this task is to update the website’s dark theme color palette so that it reflects a new branding direction. At the moment, in the app.css file, the primary color that is defined is a shade that is close to green, which has been used as the base color for some time.
However, the design team has decided to move away from this greenish hue and instead adopt cyan as the foundation for the new color palette. As part of this task, you will need to replace the previous references to the green-based primary color with the new cyan-based palette across the dark theme styles.
-
Ask the user if this task description is good enough or if they want to add more details or change anything.
-
If the user accepts the task description, you can finish this phase. If not, ask the user to provide more instructions () and go back to step 3.
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 · 170 lines · 0 tokens per session scan A 0f3b5addced2
create-issue is a command published in the GitHub repository endorhq/rover (270 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,582 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
tldr
Re-apply TLDR rules for this turn (verdict first, no filler).
tldr-update
Update TLDR from GitHub and refresh installed agent hooks/skills/rules.
tldr-help
Quick reference card for tldr modes, slash commands, and triggers.
tldr-commit
Generate tldr-style commit message (verdict first, ≤50 char subject, why over what).
tldr-compress
Compress natural language files into TLDR format to save input tokens.
tldr-review
One-line TLDR PR review comments (verdict first, no filler).