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/xiaolai/nlpm/security-scangit clone --depth 1 https://github.com/xiaolai/nlpmWhat 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.00025 | $0.00444 |
| Opus 5 | $0.00013 | $0.00222 |
| Sonnet 5 | $0.00005 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
security-scan 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.
What it actually says
Security Scan
Scan a plugin or skill repo for security risks before auditing or contributing.
Step 1: Parse Input
If arguments provided: use as target directory path. If no arguments: use the current working directory.
Check the target exists and contains at least one of:
.claude-plugin/agents/commands/skills/hooks/scripts/
If none found: report "Not a Claude Code plugin directory" and stop.
Step 2: Dispatch Security Scanner
Dispatch the security-scanner agent on the target directory.
Wait for the agent to complete and collect its report.
Step 3: Present Results
Display the full report in this exact structure: the agent report as the body, followed by the gate banner as the footer. The security-scanner agent emits the body; this command appends only the banner.
{security-scanner agent report — verbatim}
────────────────────────────────────────────────────────────
{GATE BANNER — chosen per recommendation, see below}
────────────────────────────────────────────────────────────
Gate banners:
If the recommendation is BLOCK:
SECURITY GATE: BLOCKED
Critical/High security findings. Do NOT install or contribute to this plugin without resolving these findings first.
If the recommendation is REVIEW:
SECURITY GATE: REVIEW NEEDED
Medium-severity findings detected. Review the findings before proceeding.
If the recommendation is PASS:
SECURITY GATE: PASSED
No Critical/High security findings. Safe to proceed with audit and contribution.
Error handling:
- Target path does not exist → "Directory not found: {path}"
security-scanneragent returns no report → "Security scan failed: no report produced. Re-run /nlpm:security-scan {path}."
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 · 69 lines · 25 tokens per session scan A 91faff359118
security-scan is a command published in the GitHub repository xiaolai/nlpm (133 stars, last pushed 2d ago), licensed ISC. It adds 25 tokens to every session and 444 once invoked, about $0.0001 per session on Opus 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
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.