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 skills add SauceTaster/assemblyline-mcp --skill assemblyline-triagegit clone --depth 1 https://github.com/SauceTaster/assemblyline-mcpWrote 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.
[](https://agentmods.dev/skills/saucetaster/assemblyline-mcp/assemblyline-triage)<a href="https://agentmods.dev/skills/saucetaster/assemblyline-mcp/assemblyline-triage"><img src="https://agentmods.dev/badge/skills/saucetaster/assemblyline-mcp/assemblyline-triage/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.
<a href="https://agentmods.dev/skills/saucetaster/assemblyline-mcp/assemblyline-triage"><img src="https://agentmods.dev/badge/skills/saucetaster/assemblyline-mcp/assemblyline-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00075 | $0.00757 |
| Opus 5 | $0.00037 | $0.00378 |
| Sonnet 5 | $0.00015 | $0.00151 |
| Haiku 4.5 | $0.00007 | $0.00076 |
Grade A, and why
assemblyline-triage 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 8d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AssemblyLine triage
Optional. The
assemblyline-mcpserver already ships these workflows as MCP prompts (triage_file,investigate_hash,review_alert). This skill is a richer, Claude-specific version of the same guidance. The server is fully usable without it.
You triage malware/suspicious files through the assemblyline-mcp tools. Prefer the
high-level tools; drop to raw tools only when you need detail they don't expose.
Scoring (how to read a verdict)
AssemblyLine assigns a max_score. Verdict bands use the deployment's configured
thresholds (defaults below; negative = safelisted). Always report the verdict
field from the digest — don't hard-code a number (a deployment may customize the
thresholds; check al_help_configuration).
| Score | Verdict |
|---|---|
< 0 |
safe (safelisted) |
0–299 |
informative |
300–699 |
suspicious |
700–999 |
highly suspicious |
>= 1000 |
malicious |
Triage a file or hash
al_analyze— passsha256=for a 64-hex hash,url=for a URL, orcontent_base64=for raw bytes. It submits, waits, and returns a digest. If it returnsstate="processing", pollal_submission_digest(sid=...)until done.- Report from the digest: verdict + max_score, the flagged services and notable heuristics / AV detections, the network IOCs (domains, IPs, URIs), and any extracted children (with their types). Call out errored services.
- To go deeper on a child or a specific service, use
al_file_result,al_file_strings, oral_submission_full.
Investigate / pivot on an indicator
al_submission_iocs(sid)to pull the indicator set from a submission.al_find_related(indicator=...)to find related submissions/files/alerts for a hash, domain, IP, or URL. Pivot on the strongest IOCs to map related activity.
Review an alert
al_alert(alert_id)→ score, file, status, and the linked submissionsid.al_submission_digest(sid=...)for the verdict and findings.- Conclude true/false positive with reasoning grounded in the score and findings.
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.
- 8d ago First seen · 67 lines · 75 tokens per session scan A 5cea5c0eb608
assemblyline-triage is a skill published in the GitHub repository SauceTaster/assemblyline-mcp (0 stars, last pushed 4d ago), licensed MIT. It adds 75 tokens to every session and 757 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…