Borrowing it
Nothing to install: this file belongs to elixpo/claudeOps.elixpo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/elixpo/claudeOps.elixpo/main/.claude/commands/respond-to-issue.mdgit clone --depth 1 https://github.com/elixpo/claudeOps.elixpoWrote 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/elixpo/claudeops.elixpo/respond-to-issue)<a href="https://agentmods.dev/commands/elixpo/claudeops.elixpo/respond-to-issue"><img src="https://agentmods.dev/badge/commands/elixpo/claudeops.elixpo/respond-to-issue/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/elixpo/claudeops.elixpo/respond-to-issue"><img src="https://agentmods.dev/badge/commands/elixpo/claudeops.elixpo/respond-to-issue.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.00000 | $0.00949 |
| Opus 5 | $0.00000 | $0.00475 |
| Sonnet 5 | $0.00000 | $0.00190 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
respond-to-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 12d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Respond to an issue triggered by @elixpoo mention or the ELIXPO label.
Step 1 — Load context
- Read
.elixpo-context/context.mdONCE. Don'tls/find/treeto rediscover what's there. gh issue view <n> --commentsONCE. Don't repeat with different--jsonflags.- Do NOT re-read README.md or CLAUDE.md unless the context snippet is truncated.
Step 2 — Classify the request
Look at what the user actually asked. Pick ONE:
- QUESTION / DISCUSSION / LGTM — user wants an answer, not a code change. → Go to Step 3 (answer path).
- IMPLEMENTATION — user asked for a fix, feature, refactor, or any code change. → Go to Step 4 (implement path).
- UNCLEAR — the ask is too vague to act on (missing scope, conflicting requirements). → Go to Step 5 (clarify path).
Step 3 — Answer path
Post ONE comment on the issue. That's it. No branch, no PR.
gh issue comment <n> --body "<your answer>"
Within this invocation, stop after one successful comment. The command returns empty/short stdout on success — that IS success. Do NOT retry, do NOT post a second comment "to add more", do NOT follow up with another gh call. If the user wants more, they'll ping @elixpoo again — each new trigger is a fresh invocation.
Answer rules:
- Bullets over paragraphs. <150 words.
- Link specific files/lines (
src/lib/jwt.ts:42) instead of describing. - No "I think" / "maybe". Either it's true or it's not.
- If the question has a definitive answer in AGENTS.md or the code, quote/link it.
Step 4 — Implement path
Before touching code, check for an existing linked PR:
gh pr list --search "linked:issue-<n>" --state open --json number,headRefName,title
4a. Open PR exists
Someone (possibly you, earlier) already has a PR open for this issue.
git fetch origin && git checkout <headRefName> && git pull- Make changes on that branch.
- Follow
.claude/commands/commit-push-pr.mdStep 2 (commit + push). Do NOT open a new PR. - Comment on the issue:
pushed more changes to #<pr-n>.
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.
- 12d ago First seen · 87 lines · 0 tokens per session scan A 0720b5b69fb5
respond-to-issue is a command published in the GitHub repository elixpo/claudeOps.elixpo (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 949 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-31.
Other commands, from other repositories
init-project
Initialize project with CLAUDE.md template - adaptive detection for new or existing projects.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
status
Summarise what Fabrik is doing right now — board state, in-flight workers, worktrees with uncommitted changes.
handoff
Create a handoff document for seamless session continuity.
update-docs
Scan for recently modified files and update corresponding documentation.
resume-project
Run resume-project now — Now / Blocked / Next. Not a cheat sheet.