Aleksandr Shulgin

@aleksandr-nfa.bsky.social

Python + AI agents in production. ~15 services on my own servers, most built and run solo. Open-source tools (MIT) and post-mortems of what actually broke - not launch posts. shulgin.is-a.dev

25 trending GitHub repos, checked file by file. Three were actually skill-sized. Source-to-skill tools share one hole: a README is untrusted text until you compress it into instructions your agent obeys. Built the gate instead. github.com/Sanexxxx777/evidence-to-skill

Built a tool that draws a multi-agent run from its own journal: execution map, real timeline, critical path. On the demo run 59 of 85 seconds sit on a chain of 3 nodes - more agents would not have helped. Open source, no deps: https://github.com/Sanexxxx777/agent-graph-inspector

I gave my terminal a face - a GLSL shader on the Ghostty background showing what my AI agent is doing. Thinking, working, waiting, done - and an ASCII aquarium when idle: fish, seaweed, a crab, a sleeping turtle. Zero daemons, zero tokens. MIT: github.com/Sanexxxx777/ghostty-agent-face

Shipped AI Job Search Bots: 3 production-tested Python agents for HH, LinkedIn, and remote job boards. Strict session checks, pagination, language-aware filtering, LLM scoring, deduplication, and human review. Sanitized public repo: https://github.com/Sanexxxx777/ai-job-search-bots

AI Job Search Bots: three production-tested agents in one repository

Got hacked: a weak password on an exposed remote-desktop port let an attacker pivot across my servers and drain funds (~$7k, me + a friend). Rebuilt everything and wrote down every lesson in a free hardening playbook: github.com/Sanexxxx777/server-hardening-playbook