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/william2333zz/trustshell/static-scangit clone --depth 1 https://github.com/William2333ZZ/trustshellWhat 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.00032 | $0.00298 |
| Opus 5 | $0.00016 | $0.00149 |
| Sonnet 5 | $0.00006 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
static-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 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
Run TrustShell's static engine over the target agent's source and interpret the results.
Target source directory: $ARGUMENTS (if empty, ask the user which agent source to scan).
Steps:
- From the plugin root, run the static engine on the target:
python3 "${CLAUDE_PLUGIN_ROOT}/scanner/static_scan.py" --source "$ARGUMENTS" --json - Parse the JSON. For each finding, report: the RT class (RT-1..RT-9 / RT-GUARD), the file and symbol, and one line on why it's a candidate path.
- Be honest about what this is: triage, not a verdict. A flagged path is a CANDIDATE — the static engine says "attack here," it does NOT say "this is exploitable." Say so explicitly.
- Recommend the highest-value candidates to confirm dynamically, and tell the user they can run
/red-teamto attack the running agent and prove which candidates are real.
Do not overstate. Never call a candidate a vulnerability until an exploit confirms it.
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 · 22 lines · 32 tokens per session scan A def3277bbd1c
static-scan is a command published in the GitHub repository William2333ZZ/trustshell (1 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 298 once invoked, about $0.0002 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-31.
Other commands, from other repositories
notify-authors
Open GitHub issues on flagged repos to notify authors before public disclosure.
scan-skill
Scan a specific MCP skill by npm package name or GitHub URL.
scan-daily
Run incremental ecosystem scan: crawl registries → audit new packages → merge results → generate posts.
adrian-status
Show Adrian security status - backend URL, key presence, and connection health.
wrap-up
End-of-session handoff — summarize, verify, and stage so you can review and commit.
nuguard-init
Initialise nuguard.yaml, canary.example.json and cognitive-policy.md in the current project.