jev-pruner — security grade SAFE, quality 63/100

Security audit verdict: SAFE · quality 63/100

No red flags found in any of the 11 categories — no credential harvesting, no data exfiltration, no curl-pipe-shell installer. Scanned against the SlowMist agent-security taxonomy, refreshed every 8 hours. Full audit →

by tamaratran · AI Tool · ★ 121

Last updated: · Indexed by AgentSkillsHub · Auto-synced every 8h

🔒 Is jev-pruner safe to install? View the security audit →

About jev-pruner

jev-pruner A Claude Code plugin that uses TypeSafe's Jev to trim noisy Bash output after the command runs, but before its result is sent back to the main LLM. This reduces the output carried into later turns without generating a summary. Using Codex? See Codex installation and usage. A hook wraps the Bash tool's result. Stdout of 10,000 estimated tokens or fewer passes through untouched, without reading history, writing an archive, or calling Jev. The gate uses on raw stdout, not a character count or an exact model tokenizer. can raise this threshold but cannot lower it. If Claude already saved the output to a file, the hook reads and counts that full output instead of its short preview. Errors, JSON/XML/YAML/diff/binary output, whole-document commands (, , , , , and ) are left untouched. Output is split into chunks of lines, capped at 200 chunks; lines longer than 2,000 characters are split first. Jev receives , plus and for recognized build/test/install or search/excerpt commands, and one noul question per chunk: “does any line in this chunk need to remain available?”. A single needed line protects the chunk, includin

Quick Facts

Stars121
Forks8
LanguageTypeScript
CategoryAI Tool
LicenseMIT
Quality Score63.0700556378063/100
Open Issues12
Last Updated2026-09-20
Created2026-09-18
Platformsclaude-code, node
Est. Tokens~21k

Compatible Skills

These tools work well together with jev-pruner for enhanced workflows:

  • jev-mcp — semantic(0.46)+complementary+same_lang+similar_pop+shared_platform (66%)

jev-pruner alternative? Top 4 similar tools

Looking for a jev-pruner alternative? If you're comparing jev-pruner with other ai tool tools, these 4 projects are the closest alternatives on Agent Skills Hub — ranked by topic overlap, star count, and community traction.

  • SciToolAgent by HICAI-ZJU · ⭐ 416

    SciToolAgent: A Knowledge Graph-Driven Scientific Agent for Multi-Tool Integration

  • redesigned-pancake by Sfedfcv · ⭐ 256

    Skip to content github / docs Code Issues 80 Pull requests 35 Discussions Actions Projects 2 Security Insights

  • claude-code-voice-skill by abracadabra50 · ⭐ 169

    Skill to talk to Claude about your projects over the phone

  • maui-skills by davidortinau · ⭐ 163

    .NET MAUI skills for GitHub Copilot and Claude Code

More AI Tool Tools

Explore other popular ai tool tools:

View all AI Tool tools →

Popular TypeScript Agent Tools

Frequently Asked Questions

What is jev-pruner?

jev-pruner is Claude Code plugin: trim long Bash output with TypeSafe Jev before the model sees it. It is categorized as a AI Tool with 121 GitHub stars.

What programming language is jev-pruner written in?

jev-pruner is primarily written in TypeScript.

How do I install or use jev-pruner?

You can find installation instructions and usage details in the jev-pruner GitHub repository at github.com/tamaratran/jev-pruner. The project has 121 stars and 8 forks, indicating an active community.

What license does jev-pruner use?

jev-pruner is released under the MIT license, making it free to use and modify according to the license terms.

What are the best alternatives to jev-pruner?

The top alternatives to jev-pruner on Agent Skills Hub include SciToolAgent, redesigned-pancake, claude-code-voice-skill. Each offers a different approach to the same problem space — compare them side-by-side by stars, quality score, and community activity.

How this security grade is produced

Grades come from a rule-based scan built on the SlowMist agent-security taxonomy, covering 11 red-flag categories including credential harvesting, data exfiltration, and curl | sh installers. It is a first-layer scan, not a manual audit — we say so rather than overstate it.

The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.

Sources & who's responsible:

View on GitHub → Browse AI Tool tools