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/khaitrang1995/claude-code-structure/fix-issuegit clone --depth 1 https://github.com/KhaiTrang1995/claude-code-structureWhat 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.00198 |
| Opus 5 | $0.00000 | $0.00099 |
| Sonnet 5 | $0.00000 | $0.00040 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
fix-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 yesterday.
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
/project:fix-issue – Fix Issue Command
Usage
/project:fix-issue <issue-id or description>
Description
Automated workflow to diagnose and fix a reported issue:
- Reproduce – Understand the bug from the issue description or test case
- Locate – Find the relevant file(s) and line(s) causing the problem
- Fix – Apply the minimal change needed; do not refactor unrelated code
- Verify – Run existing tests; add a regression test if none covers the bug
- Summarize – Provide a concise explanation of root cause and fix
Shell Steps
# Run tests after fix
npm test
# Check for lint errors
npm run lint
Notes
- Follow coding conventions in
.claude/rules/code-style.md - New tests must follow
.claude/rules/testing.md
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.
- yesterday First seen · 29 lines · 0 tokens per session scan A f53c1f531ce3
fix-issue is a command published in the GitHub repository KhaiTrang1995/claude-code-structure (1 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 198 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
README
Git workflow and quality assurance commands for the claude-skills repository.
plugin-audit
Run the full 8-phase plugin audit pipeline on a skill directory.
update-docs
Update all the documentation related files.
seo-auditor
Scan and optimize docs for SEO — meta tags, readability, keywords, broken links, sitemap.
review
Run the local review gate before pushing.
pr
Create a pull request from the current branch.