Borrowing it
Nothing to install: this file belongs to design-and-deliver/claude-code-autoconfig. 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/design-and-deliver/claude-code-autoconfig/main/.claude/commands/submit-claude-code-github-issue.mdgit clone --depth 1 https://github.com/design-and-deliver/claude-code-autoconfigWrote 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/design-and-deliver/claude-code-autoconfig/submit-claude-code-github-issue)<a href="https://agentmods.dev/commands/design-and-deliver/claude-code-autoconfig/submit-claude-code-github-issue"><img src="https://agentmods.dev/badge/commands/design-and-deliver/claude-code-autoconfig/submit-claude-code-github-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/design-and-deliver/claude-code-autoconfig/submit-claude-code-github-issue"><img src="https://agentmods.dev/badge/commands/design-and-deliver/claude-code-autoconfig/submit-claude-code-github-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.00852 |
| Opus 5.5 | $0.00000 | $0.00341 |
| Sonnet 5.5 | $0.00000 | $0.00170 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
submit-claude-code-github-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 2mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File a GitHub issue on the anthropics/claude-code repository, with due diligence.
Usage:
/submit-claude-code-github-issue- Start the workflow/submit-claude-code-github-issue plan names should be meaningful- Start with context from arguments
Arguments: $ARGUMENTS
Workflow:
Phase 1: Understand the Issue
- Ask the user what the issue is about, OR use any context/description provided in the arguments
- Summarize the core request in 1-2 sentences to confirm understanding
Phase 2: Due Diligence — Search Existing Issues
-
Search for similar/duplicate issues using multiple keyword variations:
gh search issues --repo anthropics/claude-code "<keywords>" --limit 15- Also search closed issues:
gh search issues --repo anthropics/claude-code "<keywords>" --state closed --limit 10
-
Categorize each result by match strength:
- Exact — Same issue, same ask. Filing would be a duplicate.
- Strong — Very similar issue, minor differences in scope or framing.
- High — Related topic, but meaningfully different request or context.
- Discard anything below High — don't show medium/low matches.
-
Present findings in a markdown table:
# Match Status Title URL 1234 Exact Open Plan filenames should be descriptive https://... 987 Strong Closed Allow custom names for plan files https://... -
Based on findings, offer options via AskUserQuestion:
- If Exact match (open): Recommend upvote + optional comment. Options: "Upvote + Comment", "File new anyway", "Cancel"
- If Exact match (closed): Note it was closed, recommend filing new if still relevant or commenting to reopen. Options: "File new", "Comment on closed issue", "Cancel"
- If Strong/High matches only: Show table, note the differences, let user decide. Options: "File new", "Comment on existing", "Cancel"
- If No matches: Proceed directly to Phase 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.
- 2mo ago First seen · 63 lines · 0 tokens per session scan A 36603d639f40
submit-claude-code-github-issue is a command published in the GitHub repository design-and-deliver/claude-code-autoconfig (2 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 852 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
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
deploy
Deploy application with pre/post-deploy checks.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
git-ops
Git + worktree orchestrator entry point. /git-ops --landall surveys every branch/worktree and batch-lands the ones that are done; bare /git-ops runs a status survey. Thin router over the git-ops skill.
branch
Show Claude Code costs per git branch / PR.