scans

scans is a command for coding agents from gotempsh/temps. It costs 0 tokens per session (855 once invoked), scanned A, original, Apache-2.0.

A command group for managing vulnerability scans, which check a project for known security weaknesses. It can show scans and the vulnerabilities they found.

In plain words
What is it for?
Starting scans, listing or inspecting results, viewing vulnerabilities, finding scans by deployment, and deleting scans.
Why use it?
It helps you identify security problems in a project and track scan results across deployments and environments.

Command

Install

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.

agentmods
npx agentmods add commands/gotempsh/temps/scans
Clone the repo
git clone --depth 1 https://github.com/gotempsh/temps

Wrote 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.

agentmods badge for scans

README.md
[![agentmods](https://agentmods.dev/badge/commands/gotempsh/temps/scans.svg)](https://agentmods.dev/commands/gotempsh/temps/scans)
Your own site
<a href="https://agentmods.dev/commands/gotempsh/temps/scans"><img src="https://agentmods.dev/badge/commands/gotempsh/temps/scans.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 855 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00855
Opus 5 $0.00000 $0.00428
Sonnet 5 $0.00000 $0.00171
Haiku 4.5 $0.00000 $0.00085

Measured 2d ago against content hash 7e1e6553ffa5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

scans 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.

skills/temps/references/commands/scans.md · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

scans command reference

Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.

scans (alias: scan)

Manage vulnerability scans

Subcommands:

  • list (ls) - List vulnerability scans for a project
  • trigger - Trigger a new vulnerability scan
  • latest - Get the latest scan for a project
  • environments (envs) - Get latest scans per environment
  • show - Show scan details
  • vulnerabilities (vulns) - List vulnerabilities found in a scan
  • remove (rm) - Delete a vulnerability scan
  • by-deployment - Get the scan for a specific deployment

scans list (alias: ls)

List vulnerability scans for a project

Options:

Flag Description Default Required
--project-id <id> Project ID - Yes
--page <n> Page number - No
--page-size <n> Items per page (default: 20, max: 100) - No
--json Output in JSON format - No

scans trigger

Trigger a new vulnerability scan

Options:

Flag Description Default Required
--project-id <id> Project ID - Yes
--environment-id <id> Environment ID to scan - Yes

scans latest

Get the latest scan for a project

Options:

Flag Description Default Required
--project-id <id> Project ID - Yes
--environment-id <id> Filter by environment ID - No
--json Output in JSON format - No

scans environments (alias: envs)

Get latest scans per environment

Options:

Flag Description Default Required
--project-id <id> Project ID - Yes
--json Output in JSON format - No

scans show

Show scan details

Read the full file on GitHub · 114 lines

Changes

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.

  1. 2d ago First seen · 114 lines · 0 tokens per session scan A 7e1e6553ffa5

Subscribe to this mod's changes

scans is a command published in the GitHub repository gotempsh/temps (712 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 855 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-09-03.