Steal Commands from Your AI Coding Agent (Your Ego Will Survive)

Look, I know you're an elite hacker. You've got the commands memorized. You can navigate a codebase with your eyes closed. You're great at what you do.

But here's what keeps happening: Your AI coding agent drops some obscure command you've never seen before. Something that does in one line what you've been doing in five. Or uses flags you didn't know existed. Or combines tools in ways that make you think "wait, you can DO that?"

And then what? You use it once, move on, and forget about it.

You're literally paying for access to these AI tools and letting the knowledge evaporate.

Here's What I Actually Do

Every time Claude Code or my AI coding assistant runs a command that makes me go "huh, interesting," I steal it. Takes about 5 seconds.

If you're using fish shell or a tool like atuin that saves your complete command history, you already have everything you need. The command is sitting right there in your history, waiting to be reused.

No fish? No atuin? Just copy-paste the good stuff into a note somewhere. A gist. A markdown file. Literally anywhere that's not /dev/null.

What You Get

• Commands that actually solve your problems (AI found them for YOUR specific use case)
• One-liners you can reuse instead of asking AI again
• Actual ROI on your AI subscription
• A personal command library that grows with every session
• The satisfaction of being more effective instead of more proud

Real Examples Worth Stealing

Git Commands You Didn't Know You Needed

AI showed me this beauty when I was trying to find which commit introduced a bug:

git log -S "function_name" --source --all

Searches through entire git history for when specific code appeared or disappeared. I had been doing this with grep and manual bisecting like a caveman.

Another one:

git diff --name-only main...HEAD | xargs wc -l

Shows exactly how many lines changed in your branch. Perfect for "is this PR going to be a nightmare to review?"

File Operations That Actually Make Sense

Claude suggested this when I needed to find large files:

fd -t f -x du -h {} \; | sort -rh | head -n 20

I had been using find with a bunch of flags I could never remember. This is clearer and faster.

For quick batch renaming:

fd -e jpg -x mv {} {.}_backup.jpg

Renames all JPGs to add "_backup" before the extension. No more writing bash loops.

Process Management Shortcuts

When my dev server wouldn't stop:

lsof -ti:3000 | xargs kill -9

Finds and kills whatever's on port 3000. I used to look up the PID manually every time.

Nix/NixOS Power Moves

AI dropped this when I needed to check what would update:

nix-store --query --requisites /run/current-system | wc -l

Shows how many packages are in your current NixOS generation. Great for "why is this rebuild taking forever?"

For cleaning up old generations:

nix-env --list-generations --profile /nix/var/nix/profiles/system | head -n -2 | awk '{print $1}' | xargs -I {} sudo nix-env --profile /nix/var/nix/profiles/system --delete-generations {}

I would have never constructed this myself, but now it's in my history forever.

JSON/Data Wrangling

When parsing API responses:

curl -s https://api.example.com/data | jq -r '.items[] | select(.status=="active") | .name'

I knew jq existed but always forgot the syntax. Now I have real examples to copy from.

"But Justin, How Will My Ego Know I'm Smarter Than AI?"

It won't. And that's fine.

Your ego doesn't ship code. Your ego doesn't meet deadlines. Your ego doesn't solve problems.

Think about how you learn from coworkers. Someone shows you a better way to do something, and you adopt it. You don't refuse their technique because "I should have thought of that myself."

AI coding agents are like having an extremely knowledgeable coworker who never gets tired of showing you new tricks. Except this coworker costs you $20/month and you can ask them stupid questions at 2am.

Actually use what you're paying for.

How to Make This Automatic

Option 1: Use fish shell (my preference)

Fish saves your command history with timestamps and directory context. Just press up arrow and search. Every command AI runs is already saved.

# Install on NixOS
nix-shell -p fish

# Or add to your configuration.nix
programs.fish.enable = true;

Option 2: Use atuin

Atuin is like fish history on steroids. Full-text search across all your commands, synced across machines, with context about when and where you ran them.

# Quick install
curl --proto '=https' --tlsv1.2 -LsSf https://setup.atuin.sh | sh

# NixOS users
programs.atuin.enable = true;

Option 3: Manual but effective

Create a file called ~/commands-i-stole-from-ai.md and paste stuff in there. Add a comment about what it does. When you need it, grep the file.

# Quick search your stolen commands
grep -i "git" ~/commands-i-stole-from-ai.md

Why This Actually Matters

Some people worry about "losing their edge" with Claude Code or Cursor. Like using AI will make them worse at coding.

That's backwards.

You're not losing your edge - you're sharpening it with someone else's whetstone. Every command you steal is a command you now know. Every clever flag combination is pattern you can recognize and modify.

The developers who thrive are the ones who learn from everyone and everything. Your AI coding agent is giving you personalized, context-specific commands for YOUR codebase and YOUR problems.

Keeping that knowledge is literally free. Not keeping it is leaving money on the table.

Start Right Now

Takes 2 minutes:

1. Install fish or atuin (or just make that markdown file)
2. Next time your AI runs a command you like, make a mental note
3. Look it up in your history later
4. Use it again tomorrow without asking AI

You're paying for these tools. Extract every bit of value you can. Your future self will thank you when you're typing that perfect command from memory instead of asking AI to remember it for you.

Be effective. Not proud.

Photo by Joshua Sortino on Unsplash