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/fotoetienne/gru/respondgit clone --depth 1 https://github.com/fotoetienne/gruWhat 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.00009 | $0.00354 |
| Opus 5 | $0.00005 | $0.00177 |
| Sonnet 5 | $0.00002 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
respond 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.
What it actually says
Respond to all comments and reviews on a GitHub pull request.
Pull Request: $ARGUMENTS
Workflow:
1. Fetch Comments and Reviews
- Use
gh pr view $ARGUMENTSto get PR details - Use
gh api repos/{owner}/{repo}/pulls/{pr#}/commentsto fetch all review comments - Use
gh api repos/{owner}/{repo}/issues/{pr#}/commentsto fetch all issue comments
2. Review All Feedback
- Read through all comments and reviews
- Identify questions, concerns, or suggestions that need responses
- Group related comments together
3. Draft Responses
- For each comment or review, draft a thoughtful response
- Address concerns directly
- Provide clarifications where needed
- Acknowledge suggestions and indicate if/how they'll be addressed
4. Post Responses
- Use
gh pr comment $ARGUMENTS -b "response content"for each response
5. Update Code
- For each response, update the code accordingly
- Commit changes with a descriptive message prefixed with your Minion ID (from the branch name), e.g.
[M042] Address review feedback - Push changes to the branch
6. Post follow-up
- After commiting updates, use
gh pr comment $ARGUMENTS -b "update content"to post a follow-up comment
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 · 38 lines · 9 tokens per session scan A 534e99cd5c38
respond is a command published in the GitHub repository fotoetienne/gru (11 stars, last pushed 25d ago), licensed Apache-2.0. It adds 9 tokens to every session and 354 once invoked, about $0.0000 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
roadmap-suggest
Mine the repo for new roadmap items — or, on a fresh project, bootstrap the board from scratch.
roadmap-sequence
Report or assemble a Sideboard sequence for the given issue numbers (targeted modes).
roadmap-cleanup
Scan the roadmap for issues that are already done or redundant, and propose closing/merging them.
roadmap
Open the Sideboard roadmap board in the preview pane.
speckit-implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit-specify
Create or update the feature specification from a natural language feature description.