tighten-your-output

tighten-your-output is a skill for Claude Code, Codex from melodic-software/claude-code-plugins. It costs 102 tokens per session (1,200 once invoked), scanned A, original, MIT.

A guide for shortening explanations and code while keeping their meaning, clarity, tests, error handling, and project conventions.

In plain words
What is it for?
Use it to trim verbose messages, documentation, or implementation details without sacrificing correctness.
Why use it?
Long or duplicated output makes important information harder to find and maintain. It helps remove wording or code that adds no value.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the discipline plugin — 16 skills shipped together

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 skills/melodic-software/claude-code-plugins/tighten-your-output
Any agent
npx skills add melodic-software/claude-code-plugins --skill tighten-your-output
Clone the repo
git clone --depth 1 https://github.com/melodic-software/claude-code-plugins

Made for: Claude Code, Codex.

Or install discipline, the plugin that ships this one along with the rest of its 16 skills.

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 tighten-your-output

README.md
[![agentmods](https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/tighten-your-output.svg)](https://agentmods.dev/skills/melodic-software/claude-code-plugins/tighten-your-output)
Your own site
<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/tighten-your-output"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/tighten-your-output.svg" alt="Measured on agentmods" height="20"></a>
Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,200 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 $0.00102 $0.01200
Opus 5 $0.00051 $0.00600
Sonnet 5 $0.00020 $0.00240
Haiku 4.5 $0.00010 $0.00120

Measured yesterday against content hash de0aa024926a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tighten-your-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 yesterday.

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.

plugins/discipline/skills/tighten-your-output/SKILL.md · 106 lines

How it starts

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

Tighten your output

A drift corrector for terseness discipline. The method, re-anchor, audit the work in flight, correct forward, report, and the tone that firing this is not an accusation, lives in ${CLAUDE_PLUGIN_ROOT}/context/re-anchor-audit-correct.md. Read it; this file adds only what is specific to terseness discipline.

The discipline this re-anchors

Say it in fewer words or lines when nothing of value is lost. Two surfaces, resolved separately per the method doc's ladder.

Code, a standards convention owns this

The source of truth is the consuming organization's simpler-code convention: prefer the smaller form when it costs no correctness, readability, test coverage, observability, or convention conformance. Read it where it lives; re-anchor its two load-bearing parts rather than restating them:

  • its named failure modes, the canonical smells a reduction must not introduce (speculative generality, the wrong abstraction, YAGNI);
  • its constraints never traded for line count. Clarity, test coverage, error handling at boundaries, established conventions, and observability survive every cut.

When the consuming project declares no such convention, re-anchor that same shape as the portable baseline: fewer lines is the default only when none of those constraints is spent to get there.

Markdown. No standards doc yet (flagged gap)

Say the same thing in fewer words with no semantic loss. Drop filler, hedging, and restatement, never a directive, qualifier, threshold, or example. Unlike the code side, prose terseness usually has no dedicated standards convention to discipline: when the consuming project's standards source declares one, route through it; when it does not, treat that as a flagged gap (a candidate upstream standards addition), not license to invent a rubric in this skill. The operative safety net for prose reduction is a compress capability's semantic-diff discipline. Route batch prose work there when that capability is installed, and otherwise run that same discipline in-thread rather than hand-rolling criteria here.

Read the full file on GitHub · 106 lines

Files

What ships with it

1 file 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. yesterday First seen · 106 lines · 102 tokens per session scan A de0aa024926a

Subscribe to this mod's changes

tighten-your-output is a skill published in the GitHub repository melodic-software/claude-code-plugins (15 stars, last pushed today), licensed MIT. It adds 102 tokens to every session and 1,200 once invoked, about $0.0005 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-09-03.

Related

Other skills, from other repositories

linkedin-engine

Daily interactive LinkedIn session: feed posts, DM outreach, prospect research, engagement tracking, and performance review. Human-in-the-loop. Designed for daily /loop.

systempromptio/systemprompt-marketplace · 36 tokens

reddit-reply

Daily follow-up on Reddit engagement. Reads recent reddit-monitor reports, checks each URL for replies to our comments, and drafts follow-up responses. Designed for daily /loop. Load identity and brand-voice first.

systempromptio/systemprompt-marketplace · 46 tokens

social-media-guide

Entry point for social-media — routes to LinkedIn, Reddit, X/Twitter, and the daily social brief.

systempromptio/systemprompt-marketplace · 26 tokens

parallel-orchestrator

Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…

jimmc414/claude-code-plugin-marketplace · 78 tokens

parallel-worker

Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.

jimmc414/claude-code-plugin-marketplace · 59 tokens

propagate-then-search

For constraint problems: eliminate impossibilities before guessing, reduce search space through inference, fail fast on contradictions.

jimmc414/claude-code-plugin-marketplace · 27 tokens