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/Dev-GOM/claude-code-marketplaceWrote 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/dev-gom/claude-code-marketplace/suggest)<a href="https://agentmods.dev/commands/dev-gom/claude-code-marketplace/suggest"><img src="https://agentmods.dev/badge/commands/dev-gom/claude-code-marketplace/suggest/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/dev-gom/claude-code-marketplace/suggest"><img src="https://agentmods.dev/badge/commands/dev-gom/claude-code-marketplace/suggest.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.00006 | $0.00217 |
| Opus 5.5 | $0.00002 | $0.00087 |
| Sonnet 5.5 | $0.00001 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
suggest 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.
What it actually says
Analyze the code and provide intelligent improvement suggestions.
Analysis Areas:
-
Refactoring Opportunities
- Extract repeated code into functions
- Simplify complex logic
- Remove dead code
- Improve naming
-
Design Improvements
- Better separation of concerns
- More appropriate design patterns
- Cleaner interfaces
- Reduced coupling
-
Performance Optimizations
- Algorithm improvements
- Caching strategies
- Lazy loading
- Database query optimization
-
Code Modernization
- Use newer language features
- Update deprecated APIs
- Modern best practices
-
Maintainability
- Better error handling
- Improved logging
- More comprehensive tests
- Enhanced documentation
For each suggestion:
- Explain WHY it's better
- Show BEFORE/AFTER code examples
- Estimate the impact and effort
Prioritize suggestions by importance and ease of implementation.
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 · 45 lines · 6 tokens per session scan A 6a7d183cc27f
suggest is a command published in the GitHub repository Dev-GOM/claude-code-marketplace (97 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 6 tokens to every session and 217 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
refactor
Systematic code refactoring with smart scope detection.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.