capture-acts — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited capture-acts (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Run a forward pass through the researcher's loaded model, hooking specified layers, extracting activations at named positions. Activations stay in the Colab session memory; only metadata (shape, capture_id, manifest SHA256) crosses the wire.
Before any of: probe-eval, causality-protocol, sae-lookup. These all need a capture_id.
Also when the researcher asks "what are the activations at L20 for this prompt?" or "store the residual at L11/L31/L55 for {prompt}".
Call the MCP tool `capture_acts` with:
prompt: the text to run through the modellayers: list of layer indices (e.g. [10, 20, 27])positions: list of position specs. Defaults to ["end_question"].end_question / end_prompt / last_token → last input tokenfirst_token → token 0<int> → absolute index (negative counts from end)"end_question:-2" → 2 tokens before end"Captured L{layers} × {positions} → capture_id {id[:8]}… (d_model={d}, manifest sha {sha[:12]})"Hand the capture_id to whatever comes next. Don't try to read the raw tensors; they live in the Colab session.
A single forward pass on Qwen2.5-7B at bf16 on a T4 is ~2 s; on A100 ~0.5 s. Larger models scale. Don't batch hundreds of prompts in a tight loop without warning the researcher.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.