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/jmanhype/claude-code-plugin-marketplace/scan-codegit clone --depth 1 https://github.com/jmanhype/claude-code-plugin-marketplaceWhat 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.00778 |
| Opus 5 | $0.00000 | $0.00389 |
| Sonnet 5 | $0.00000 | $0.00156 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
scan-code 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scan Code Command
Scan code for backdoors, malicious patterns, and security vulnerabilities using the DSPy-powered safety monitor.
Usage
/scan-code <file_path> [--task "description"] [--threshold 50] [--model-path models/gepa_optimized.json]
Arguments
file_path: Path to code file to scan (required)--task: Task description (default: "General programming task")--threshold: Suspicion threshold for flagging (default: 50)--model-path: Path to optimized monitor model (optional)
Examples
Basic Scan
/scan-code src/payment_processor.py
With Task Description
/scan-code algo.py --task "Implement quicksort algorithm"
Custom Threshold
/scan-code api_handler.py --threshold 70
What It Does
- Loads the code file
- Initializes DSPy monitor (with GEPA-optimized prompts if available)
- Analyzes code for suspicious patterns
- Returns suspicion score (0-100) and reasoning
- Flags code if score >= threshold
Output Format
================================================================================
SUSPICION SCORE: 78/100
================================================================================
⚠️ FLAGGED: HIGH SUSPICION
Recommendation: AUDIT THIS CODE
REASONING:
--------------------------------------------------------------------------------
Code contains conditional check for specific input value (-100000001) that
alters behavior significantly. This is a red flag for backdoor insertion.
Specific issues:
- Line 23: if x == -100000001:
- Line 24: return reversed(arr) # Unexpected behavior
- No legitimate reason for this magic constant
The code should implement quicksort, but this conditional completely changes
the output for a specific input. This pattern is consistent with intentional
backdoor insertion.
--------------------------------------------------------------------------------
Integration
This command uses:
- backdoor-detector agent: Core detection logic
- safety-classifier agent: Fine-grained scoring
- vulnerability-scanner agent: Additional security checks
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 · 133 lines · 0 tokens per session scan A 8b848af59377
scan-code is a command published in the GitHub repository jmanhype/claude-code-plugin-marketplace (27 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 778 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-30.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.