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/design-and-deliver/claude-code-autoconfig/submit-claude-code-github-issuegit clone --depth 1 https://github.com/design-and-deliver/claude-code-autoconfigWhat 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.00852 |
| Opus 5 | $0.00000 | $0.00426 |
| Sonnet 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 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 — 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.
- 2d 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 3d 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.