Show HN: Lowfat – pluggable CLI filter that saved 91.8% of my LLM tokens
8 by zdkaster | 4 comments on Hacker News.
Hi HN, Not sure if anyone would be interested. But, just wanted to share that I've been maintaining my small tool called 'lowfat' that helps me filters some of my verbose CLI output. It's a single binary, works as an agent hook or a shell wrapper.
It has a plugin system to customize filters per command. The idea is pretty simple: agents don't need the full kubectl get -o yaml or any 10k-line dump to make decisions.
So that lowfat sits in between, strips the noise, and passes through what matters. Here's my real report after 2 months of personal use: lowfat history --all lowfat plugin candidates
─────────────────────────────────────────────────────────
# command runs avg raw cost savings source status
1 kubectl get 101x 14.4K 1.5M 93.9% plugin good
2 grep 103x 13.5K 1.4M 96.2% plugin good
3 git diff 81x 995 80.6K 57.9% built-in good
4 kubectl 90x 485 43.6K 33.6% plugin good
5 docker 127x 5.5K 693.6K 96.1% built-in good
6 ls 489x 117 57.3K 56.2% built-in good
7 find 30x 16.5K 495.0K 95.5% plugin good
8 git show 63x 490 30.9K 38.0% built-in good
9 git 177x 368 65.2K 76.1% built-in good
10 git log 86x 556 47.8K 78.5% built-in good
11 kubectl logs 5x 3.6K 17.8K 43.0% plugin good
12 git status 86x 152 13.1K 58.0% built-in good
13 docker ps 20x 467 9.3K 52.8% plugin good
14 kubectl describe 6x 656 3.9K 1.2% plugin weak
15 docker images 9x 940 8.5K 61.8% built-in good
16 k get 2x 2.1K 4.2K 35.9% plugin good
17 terraform 10x 395 3.9K 32.1% plugin good
18 git commit 32x 77 2.5K 0.0% built-in weak
19 docker build 8x 487 3.9K 37.6% built-in good
20 docker compose 22x 979 21.5K 89.4% built-in good
total: 4.4M raw → 4.1M saved (91.8%)
My toolset above is kind limited, but it works pretty well for my usecase without any interruption
Kinda help me not reaching the token limit for my company Bedrock limit usage and keep optimizing the saving on the go for later usage. But, why not alternatives ( https://ift.tt/4dDLvlP ) ?
The answers are:
- My goal is to make the core lightweight but extensible via plugins i.e. not trying to bundle every command in the installed binary so that people own their output filters.
- Customizable per usecase via plugin or filter pipelines as I am using my own toolset.
- Customizable for non-public CLI tools, for example, some enterprise might have their interal CLI tools that public won't have access.
- People should own their data. So the design is local-first, No telemetry forever.
- I kinda love UNIX-style composible pipes, so lowfat-filter has implemented this style.
- Be able to adjust aggressiveness of the filter, so we can control that we won't strip something the agent needed. GitHub: https://ift.tt/4WkIXDh Anyway, if anyone is interested, feedbacks and questions are welcome! Thanks!
Friday, 5 June 2026
New top story on Hacker News: Ask HN: Is the web for machines (/llm.txt) the one we wished we had as humans?
Ask HN: Is the web for machines (/llm.txt) the one we wished we had as humans?
11 by sunshine-o | 11 comments on Hacker News.
I got really tired, as a human, of parsing the standard marketing heavy web we have today. I've always loved the simplicity of gopher and gemini web. Recently I found myself manually adding `/llm.txt` to most websites I visit because I find the content for LLMs strait to the point and clear. The only annoyance is web browsers like chrome do not render the markdown. So could the AI revolution actually fix the web for humans as a side effect? Do you find yourself doing the same?
11 by sunshine-o | 11 comments on Hacker News.
I got really tired, as a human, of parsing the standard marketing heavy web we have today. I've always loved the simplicity of gopher and gemini web. Recently I found myself manually adding `/llm.txt` to most websites I visit because I find the content for LLMs strait to the point and clear. The only annoyance is web browsers like chrome do not render the markdown. So could the AI revolution actually fix the web for humans as a side effect? Do you find yourself doing the same?
Thursday, 4 June 2026
New top story on Hacker News: Show HN: Uruky (EU-based Kagi alternative) now has Image Search and URL Rewrites
Show HN: Uruky (EU-based Kagi alternative) now has Image Search and URL Rewrites
36 by BrunoBernardino | 16 comments on Hacker News.
You can get a 2h free trial by solving a proof-of-work captcha when topping up your account for the first time. If you'd like to learn more, an independent interview was posted a couple of weeks ago [1], and the FAQ [2] has a lot of information as well. For the source code sharing, we've talked with lawyers and are inclined to no longer require the NDA/NCC for privacy reasons shared with us before (signing requires identification), but instead use a source-available permissive license that doesn't allow competition, like PolyForm Shield [3] (we do still have about 6 months before finalising a decision, here). This does come with a lot more risks for us (it's harder to track down if someone publishes the code or uses it against the license), but given we've already passed 100 monthly active accounts, we're feeling more confident it's an acceptable risk. The plan is to give logged in accounts (who are 12 months old or more) a way to download a ZIP of the current code base that's in the server. Obviously there's no easy way to prove that's the case, but we're open to ideas/suggestions if someone here has them. [1]: https://ift.tt/KyqishJ... [2]: https://uruky.com/faq [3]: https://ift.tt/K1ga9QL
36 by BrunoBernardino | 16 comments on Hacker News.
You can get a 2h free trial by solving a proof-of-work captcha when topping up your account for the first time. If you'd like to learn more, an independent interview was posted a couple of weeks ago [1], and the FAQ [2] has a lot of information as well. For the source code sharing, we've talked with lawyers and are inclined to no longer require the NDA/NCC for privacy reasons shared with us before (signing requires identification), but instead use a source-available permissive license that doesn't allow competition, like PolyForm Shield [3] (we do still have about 6 months before finalising a decision, here). This does come with a lot more risks for us (it's harder to track down if someone publishes the code or uses it against the license), but given we've already passed 100 monthly active accounts, we're feeling more confident it's an acceptable risk. The plan is to give logged in accounts (who are 12 months old or more) a way to download a ZIP of the current code base that's in the server. Obviously there's no easy way to prove that's the case, but we're open to ideas/suggestions if someone here has them. [1]: https://ift.tt/KyqishJ... [2]: https://uruky.com/faq [3]: https://ift.tt/K1ga9QL
Wednesday, 3 June 2026
Subscribe to:
Posts (Atom)