@intentic/claude-plugin weekly downloads statistics

intentic plugin for Claude Code

Trims Bash output before Claude reads it, opens each session with a map of the project and its field notes, teaches the fileq and iq CLIs, and reports what each of these saved. Every mechanism is a switch in /config.

/plugin marketplace add intentic/intentic
/plugin install intentic@intentic

The hooks and the bundled commands run on Node.js 20.11 or later, which has to be on PATH. Without it the plugin does nothing, and each session opens with one line saying so. Claude Code fetches the plugin from npm (@intentic/claude-plugin), so npm has to be installed too.

What it does

When	What happens	Switch
A session opens	Claude gets a map of the project: its areas, what each is for, and where the session started. It is recomputed from the tree for every session.	project_map
A session opens	Claude gets this project's field notes, cut by rank to 4,000 characters, if /intentic:field-notes has written them.	field_notes
A session opens	Claude is taught iq, a code search that answers a question with ranked path:line anchors, if iq is installed.	iq
A prompt is sent	iq points a prompt that matches earlier work at the session that did it.	iq
A Bash command succeeds	The output is cleaned before Claude reads it: progress bars, install chatter, repeated lines, the middle of huge logs. A footer names the command that reads the full text back.	output_cleaners, cleaners
Claude reads a document	fileq turns docx, pdf, xlsx, pptx, epub, ipynb, images, audio and archives into markdown.	fileq
Claude makes a document	fileq check lists what is wrong with a docx, pptx, xlsx or pdf by slide, page or cell, and fileq render draws its pages as PNGs for Claude to look at (with LibreOffice and poppler installed). The fileq skill says to run both before handing the file over.	fileq

| A Bash command succeeds, in Claude Code 2.1.287 or later | A line under the prompt says what the cleaners saved so far this session, and /intentic-pane shows the full report in a pane. See In the interface. | output_cleaners |

A failed command reaches Claude unchanged. Outside an Intentic sandbox there is no secret store to mask values from, so the cleaners mask only text that looks like a credential: an assignment to a name like API_KEY or TOKEN whose value looks generated, bearer tokens, AWS access keys, and passwords in URLs.

The intentic:Intentic output style adds three working habits to Claude Code's own instructions: batch independent lookups, reuse what is already in context, and run long commands in the background instead of sleeping. Pick it in /output-style. It is off until you do.

Switches

Open /config and find the rows under intentic. The switches read at session start (project_map, field_notes, iq, fileq, holdout) apply from the next session.

Key	Default	Effect
output_cleaners	on	Clean successful Bash output, ledger what each cleaner saved, and show the saving under the prompt. Off, none of the three happens
cleaners	empty (all)	Which cleaners run: -cap,-wide switches some off, git,pnpm allows only those
output_holdout	0	Share of commands left uncleaned, to measure the saving against real output
project_map	on	Send the project map at session start
field_notes	on	Send this project's field notes at session start
iq	on	Teach iq and run its session recall, when iq is installed
fileq	on	Let the bundled fileq run. Off, it refuses, and its skill stays listed because a plugin cannot hide its own skills
holdout	0.1	Share of sessions opened without the map, the notes and the iq teaching, so the report can compare

What it saved

Run /intentic:stats for this project, or /intentic:stats all for every project the plugin has seen.

## Bash output
412 commands trimmed: 1.9M tokens of output became 310k (84% saved, exact per command).
Biggest cleaners: cap 1.1M (96 commands), pnpm 210k (40 commands), dedup 88k (131 commands).

## Session context
Project map, opening turns that listed directories: -45.2% ±20.1pp (95%): 17% with it vs 31% without, over 118 and 31 opening turns.
Field notes, failed tool calls per turn: no difference yet beyond ±24.1pp (95%): 0.6 with it vs 0.7 without, over 104 and 33 conversations.
iq teaching, search calls per turn: measuring, 12 of 30 conversations in the smaller arm: 2.1 with it vs 2.9 without, over 96 and 12 conversations.

The numbers above are an illustration of the format. The report reads two things:

• The cleaners' ledger, one row per command with the bytes before and after and what each cleaner removed. That saving is exact. With output_holdout above 0 it also compares the median cleaned output against commands left uncleaned.
• Claude Code's own session transcripts, compared across the two arms each session was drawn into. A hash of the session id puts holdout of the sessions in the control arm for each mechanism, so the draw needs no state and gives the same answer every time it is read. The map is judged on the share of first turns that listed the project's directories, the field notes on failed tool calls, and the iq teaching on search calls, each counting the main agent's calls and not its subagents'. A change is stated only once both arms hold 30 samples and the 95% margin excludes zero.

The arithmetic is the one behind the savings page of an Intentic sandbox, from the same packages, so a number here means what it means there.

In the interface

Claude Code 2.1.287 and later can load a small mod from a plugin, code that runs inside Claude Code and draws in its interface. The plugin's mod (hooks/register.ts) makes the cleaners' work visible, and does nothing else: it changes no output and sends nothing.…