agentmods.dev

assay-scan

assay-scan is a command for Claude Code from chawdamrunal/assay. It costs 48 tokens per session (556 once invoked), scanned B, original, Apache-2.0.

A command that runs a five-stage, citation-checked security review on a local folder or workspace path using the Assay service.

In plain words
What is it for?
Use it to scan a plugin or other local target for security issues and produce audit files with findings and supporting file-and-line evidence.
Why use it?
It creates an evidence-based audit and checks cited file locations again before finalizing the results, reducing unsupported findings.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths; mentions Claude Code.

not rated 4repo 3mo ago B scan 48 tokens original Apache-2.0

Good fit Use it to scan a plugin or other local target for security issues and produce audit files with findings and supporting file-and-line evidence.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/chawdamrunal/assay/assay-scan
View source ↗ chawdamrunal/assay chawdamrunal.github.io
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.

Clone the repo
git clone --depth 1 https://github.com/chawdamrunal/assay

Made for: Claude Code.

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 assay-scan

README.md
[![agentmods](https://agentmods.dev/badge/commands/chawdamrunal/assay/assay-scan/github.svg)](https://agentmods.dev/commands/chawdamrunal/assay/assay-scan)
Your own site
<a href="https://agentmods.dev/commands/chawdamrunal/assay/assay-scan"><img src="https://agentmods.dev/badge/commands/chawdamrunal/assay/assay-scan/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.

agentmods 80×15 button for assay-scan

Your own site · 80×15
<a href="https://agentmods.dev/commands/chawdamrunal/assay/assay-scan"><img src="https://agentmods.dev/badge/commands/chawdamrunal/assay/assay-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 556 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00048 $0.00556
Opus 5.5 $0.00019 $0.00222
Sonnet 5.5 $0.00010 $0.00111
Haiku 4.5 $0.00005 $0.00056

Measured 2mo ago against content hash 157a5630436d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

assay-scan scanned grade B with 2 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 2mo 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.

Downloads and executes remote codemediumSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

curl -sSL https://raw.githubusercontent.com/chawdamrunal/assay/main/install.sh | sh

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sSL https://raw.githubusercontent.com/chawdamrunal/assay/main/install.sh | sh
plugin/commands/assay-scan.md · 50 lines

What it actually says

/assay-scan

Run a citation-verified 5-stage security scan against the given target by following the embedded Assay methodology via the assay MCP server.

Usage

/assay-scan <target>

Where <target> is:

  • An absolute path to a local directory (e.g., ~/.claude/plugins/my-plugin)
  • A path under the workspace

What happens

  1. Loads the assay_methodology prompt from the assay MCP server (registered via .mcp.json in this plugin).
  2. The prompt instructs you to walk the 5 stages — triage, claims, threat model (before reading code), investigation, exploitability + synthesis — calling the assay_* MCP tools at each step.
  3. At Step 0, calls assay_scan_start to allocate ~/.assay/scans/<basename>/<scan_id>/.
  4. At Steps 1-4, calls assay_list_files, assay_read_file, assay_grep, assay_parse_manifest, assay_secret_scan, and assay_osv_lookup to investigate.
  5. Every confirmed finding is appended via assay_record_finding with a verbatim file:line snippet.
  6. At Step 6, assay_finalize_scan re-reads every cited file:line, drops fabricated evidence, recomputes the verdict from what survives, and writes audit.json + audit.md.

Prerequisites

The assay binary must be on PATH and the .mcp.json in this plugin's directory must be discovered by Claude Code. Install via:

curl -sSL https://raw.githubusercontent.com/chawdamrunal/assay/main/install.sh | sh

Output

After assay_finalize_scan returns, you should see:

  • The verdict (safe / caution / unsafe)
  • The count of surviving findings by severity
  • The path to audit.md + audit.json
  • A suggestion to open assay serve (http://localhost:7373) to browse the report

Execute

Load the methodology prompt for the supplied target and follow every step in the order it specifies. The target argument is $ARGUMENTS:

@assay assay_methodology target="$ARGUMENTS"
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. 2mo ago First seen · 50 lines · 48 tokens per session scan B 157a5630436d

Subscribe to this mod's changes

assay-scan is a command published in the GitHub repository chawdamrunal/assay (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 48 tokens to every session and 556 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude CodeLLMSecurityai-securitydevsecopsmcpsecurity-scanner
Related

assay-scan compared with commands from other repositories

assay-scan next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
assay-scanchawdamrunal/assayCommand43mo agoApache-2.0B48Claude Code
sicario.assessdfirs1car1o/sicario-specCommand55d agoMITA0Claude Code
sicario.reviewdfirs1car1o/sicario-specCommand55d agoMITA0Claude Code
checklistgithub/spec-kitCommand149ktodayMITA13Claude Code
clarifygithub/spec-kitCommand149ktodayMITA27Claude Code
specifygithub/spec-kitCommand149ktodayMITA13Claude Code
convergegithub/spec-kitCommand149ktodayMITA35Claude Code