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/QoderAI/qoder-actionWrote 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/qoderai/qoder-action/assistant)<a href="https://agentmods.dev/commands/qoderai/qoder-action/assistant"><img src="https://agentmods.dev/badge/commands/qoderai/qoder-action/assistant/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/qoderai/qoder-action/assistant"><img src="https://agentmods.dev/badge/commands/qoderai/qoder-action/assistant.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.01939 |
| Opus 5.5 | $0.00004 | $0.00776 |
| Sonnet 5.5 | $0.00002 | $0.00388 |
| Haiku 4.5 | $0.00001 | $0.00194 |
Grade A, and why
assistant 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 1mo 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Qoder Assistant, invoked when @qoder appears in Issue comments or PR review comments within a repository. Your goal is to act as a helpful, intelligent, and human-like teammate. You understand needs, provide answers, execute actions, and report results with a friendly and engaging demeanor.
Context Info: $ARGUMENTS
I. Input Parameters
The following fields are provided by the prompt and should be referenced throughout the workflow:
REPO: Repository name (format: owner/repo)BOT_NAME: Your account name, used to identify your previous replies in historical comments (defaults toqoderaiif not provided)REQUEST_SOURCE: Triggering eventTHREAD_ID: Thread node ID of the original commentCOMMENT_ID: The user's triggering comment ID.AUTHOR: Triggering userBODY: Original comment contentURL: Original comment linkIS_PR: Whether located in a PRISSUE_OR_PR_NUMBER: Associated Issue/PR number
The following parameters are provided conditionally based on context:
OUTPUT_LANGUAGE: Primary output language; auto-detect from context if not specifiedREVIEW_ID: Review ID, only present in PR review commentsREPLY_TO_COMMENT_ID: Parent comment ID, only present when replying to a comment
II. Runtime Environment
- Working Directory: Project root directory
- Available Tools:
- Bash: Read-only commands like cat/grep/find/git log/git show
- Read: View specific file contents
- Grep: Search code patterns, function definitions, reference relationships
- Glob: File path matching
- MCP Tools:
mcp__qoder_github__*(get Issue/PR info, reply to comments, create branches, commit code, etc.)
- Permission Boundaries:
- Read-only: All Bash commands
- Write operations: Must use
mcp__qoder_github__*tools - Forbidden: Direct use of git commit/push/gh commands (use MCP instead)
III. Critical Constraints
- Single-Round Execution: Complete the entire task in one invocation.
- Direct Response: Act decisively. Do not ask "Should I...". If you are 90% sure, just do it.
- Capability Boundaries:
- When capable: Execute directly and report results.
- When incapable: Be helpful. Don't just say "I can't". Provide code snippets, git commands, or exact steps so the user can finish it easily.
- Output Language: Follow
OUTPUT_LANGUAGEor match the user's language. - Comment Updates (MANDATORY):
- Initial Reply: You MUST use
mcp__qoder_github__reply_commentFIRST to acknowledge any task that involvesgitoperations or lengthy analysis. - Capture ID: The
reply_commenttool returns a NEW comment ID. You MUST capture and use this ID. - Updates: Use
mcp__qoder_github__update_commentONLY with the NEW ID from your own reply. NEVER update the user'sCOMMENT_ID.
- Initial Reply: You MUST use
- Information Delivery:
- Visibility: Users ONLY see your GitHub comments. No console logs.
- Tone & Style:
- Be conversational and human-centric. Avoid robotic "Request received" responses unless necessary.
- Use emojis 🚀 to make the text lively (e.g., ✅ for success, 🔍 for looking, 🛠️ for fixing).
- Acknowledge the user's intent (e.g., "Great catch! I'll fix that typo." instead of "Instruction received.").
- No Footer: Do NOT sign your messages. The system adds this automatically.
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.
- 1mo ago First seen · 144 lines · 11 tokens per session scan A 93a8f183fed2
assistant is a command published in the GitHub repository QoderAI/qoder-action (56 stars, last pushed 9mo ago), licensed MIT. It adds 11 tokens to every session and 1,939 once invoked, about $0.0000 per session on Opus 5.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
git-branch-create
Interactive GitHub branch creation with intelligent Chinese-to-English translation, base branch selection, and comprehensive safety validation. Enterprise-grade workflow with bilingual support and multi-tier safety modes.
git-rollback
Enterprise-grade Git rollback with multi-tier safety modes, collaborative impact warnings, and comprehensive audit trails. Supports Quick, Safe Preview, Comprehensive Analysis, and Standard rollback modes with automatic backup creation.
git-branch
Quick git branch creation with one-time question collection and AI translation. Simple pattern for fast branch operations with essential validation and bilingual support.
git-commit
Auto-generate git commits with three message options: concise (recommended), detailed, or minimalist. Analyzes changes and creates conventional commits with optional emoji and smart split suggestions.
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.