distilling-tool-output

distilling-tool-output is a skill for Claude Code from Nolane-x/forge-os. It costs 35 tokens per session (177 once invoked), scanned A, original, MIT.

A method for reducing very large test, compiler, browser, database, or terminal output into a usable summary while keeping the original data retrievable. A digest is a fixed identifier used to verify that the original data has not changed.

In plain words
What is it for?
Use it to store raw output, create a digest-linked summary, and provide a retrieval location for the original bytes.
Why use it?
It keeps large outputs out of the agent's working context without losing the ability to inspect the complete evidence later.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the forgeos plugin — 196 skills, 1 command, 1 agent, 1 MCP server shipped together

Good fit Use it to store raw output, create a digest-linked summary, and provide a retrieval location for the original bytes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nolane-x/forge-os/distilling-tool-output
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.

Any agent
npx skills add Nolane-x/forge-os --skill distilling-tool-output
Clone the repo
git clone --depth 1 https://github.com/Nolane-x/forge-os

Made for: Claude Code.

Or install forgeos, the plugin that ships this one along with the rest of its 196 skills, 1 command, 1 agent, 1 MCP server.

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 distilling-tool-output

README.md
[![agentmods](https://agentmods.dev/badge/skills/nolane-x/forge-os/distilling-tool-output/github.svg)](https://agentmods.dev/skills/nolane-x/forge-os/distilling-tool-output)
Your own site
<a href="https://agentmods.dev/skills/nolane-x/forge-os/distilling-tool-output"><img src="https://agentmods.dev/badge/skills/nolane-x/forge-os/distilling-tool-output/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 distilling-tool-output

Your own site · 80×15
<a href="https://agentmods.dev/skills/nolane-x/forge-os/distilling-tool-output"><img src="https://agentmods.dev/badge/skills/nolane-x/forge-os/distilling-tool-output.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 177 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.00035 $0.00177
Opus 5 $0.00017 $0.00088
Sonnet 5 $0.00007 $0.00035
Haiku 4.5 $0.00003 $0.00018

Measured 9d ago against content hash 95d6b7ebfcb5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

distilling-tool-output 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 9d 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-v2/kernel/distilling-tool-output/SKILL.md · 23 lines

What it actually says

Distilling Tool Output

Core principle

Store raw bytes in content-addressed evidence storage. Bind the summary to the raw digest and retrieval URI. The runtime owns deterministic scope, coverage, policy, and evidence checks; the agent owns only the judgment that cannot be reduced safely to code.

Do not activate when

  • the raw output is already concise
  • the output contains binary data requiring a specialized parser
Files

What ships with it

9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 23 lines · 35 tokens per session scan A 95d6b7ebfcb5

Subscribe to this mod's changes

distilling-tool-output is a skill published in the GitHub repository Nolane-x/forge-os (10 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 177 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.

Related

Other skills, from other repositories

root-cause

Find the mechanism behind a failure instead of patching its symptom - reproduce first, one variable per experiment with the prediction written before the run, exit by naming the mechanism and pinning it with a failing test. Use for a bug, an unexplained red test, or a failure that will not reproduce.

jjanczur/tyran · 61 tokens

dos-self-improve

Run the DOS self-improvement loop: propose a candidate, verify it in an isolated worktree, measure suite/truth/metric gates, and keep only confirmed gains. Use for recursive improvement; use dos-enforce-tune for policy knobs.

anthony-chaudhary/dos-kernel · 56 tokens

add-plugin

Use when installing, disabling, enabling, or troubleshooting a third-party octomux plugin — the manifest row shape, octomux plugins list/disable/enable, reading octomux doctor output, and recovering a broken boot with --safe-mode.

ShreyPaharia/octomux · 53 tokens

create-task

Use when creating an octomux task to dispatch autonomous Claude Code agents for building features, fixing bugs, or any code changes.

ShreyPaharia/octomux · 28 tokens

dos-unstick

Analyze BLOCKED/DRAIN run history, cluster recurring causes, and propose one structural fix per wedge via dos decisions. Use when a fleet keeps stalling and you want a systemic unblock rather than another manual nudge.

anthony-chaudhary/dos-kernel · 49 tokens

quicken

Quicken the codebase — an ad-hoc performance audit that reveals what drags (N+1 queries, needless re-renders, missing caching, memory leaks, redundant computation, hot-path complexity) and prescribes the fix, surfaced inline in the session. Scoped to your current diff by default, or to a path/area you name. Use before…

eric-cielo/moflo · 0 tokens