Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install disciplineWrote 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/melodic-software/claude-code-plugins/tighten-your-output)<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/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/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="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.00102 | $0.01626 |
| Opus 5.5 | $0.00041 | $0.00650 |
| Sonnet 5.5 | $0.00020 | $0.00325 |
| Haiku 4.5 | $0.00010 | $0.00163 |
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 5d 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 — 129 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 shared method (re-anchor,
audit the work in flight, correct forward, report) 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. A flagged standards gap with a routing owner
Say the same thing in fewer words with no semantic loss. Drop filler, hedging, and restatement, never a directive, qualifier, threshold, or example. Tightening selects what to include; it does not compress prose into fragments, abbreviations, arrow chains, or jargon, and it keeps complete sentences a reader who did not watch the work can follow. When brevity and readability conflict, readability wins. Prose terseness usually has no dedicated standards convention: when the consuming project's standards source declares one, route through it; when it does not, that is a flagged gap (a candidate upstream standards addition), not license to invent a rubric in this skill. Route reader-facing prose and batch prose work per the Routing section below.
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.
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.
- 5d ago Changed · -22 lines f224e91f3551
- 1mo ago Changed · +42 lines 9fb77cb35796
- 1mo ago Changed · +3 lines a3623d93ddd8
- 1mo ago First seen · 106 lines · 102 tokens per session scan A de0aa024926a
tighten-your-output is a skill published in the GitHub repository melodic-software/claude-code-plugins (26 stars, last pushed today), licensed MIT. It adds 102 tokens to every session and 1,626 once invoked, about $0.0004 per session on Opus 5.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.
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.
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.
social-media-guide
Entry point for social-media — routes to LinkedIn, Reddit, X/Twitter, and the daily social brief.
generate-tree-structure
For tree/maze generation: spanning trees, random mazes, graph coverage. Uses frontier-based exploration with configurable traversal order.
catch-expected-errors
For iteration with errors: catch exceptions during exploration, skip invalid cases, continue to next attempt.
verify-with-inline-tests
For test co-location: tests in same file as code, run with main, tests as documentation and examples.