ivo's home

geo-score is a Python script that evaluates a web site's readiness for AI search engine citations, outputting a zero to one hundred score based on an open rubric. Running it requires only Python 3.8 and the standard library, executing a single check via a piped curl command without local installation. It inspects robots.txt, sitemaps, structured data, and content formatting to identify mechanical gaps preventing retrieval.

The script is worth running for a quick baseline on how LLMs and answer engines see your static markup, but the higher tiers require your own API keys to query actual citation behavior. It separates the static score from dynamic query checks because a high technical score does not guarantee you will actually get cited against competitors. Skip it if you are not actively trying to optimize for generative search engines like Perplexity or Gemini.

more: https://github.com/jianruntech/geo-score

MemoraX Code is a Node.js 20+ package that provides a persistent memory layer for various LLM coding agents including Claude Code, Cursor, and DeepSeek Harness. It runs locally as a background process to store repository rules, architectural history, and past engineering decisions across different sessions. The tool requires libsecret on Linux and specifically manages plugin integration for supported CLI and editor-based coding tools.

This is worth installing if you are tired of re-explaining project constraints to your AI assistant every time you open a new terminal window. It is not for users who want zero external dependencies, as it relies on a cloud-based backend for synchronization and requires careful management of API keys. If you frequently context-switch between projects, the overhead of setup is minimal compared to the time saved on redundant prompting.

more: https://github.com/memorax-ai/memorax-code

fauxnix-cli is a Node.js CLI and MCP server for Windows systems running Node 18 or later and PowerShell 5.1+. It deterministically translates bash commands into native PowerShell at runtime without LLM calls, WSL, or virtual machines. Covering 109 core utilities verified against GNU coreutils test suites, it allows AI coding agents to run standard bash pipelines directly on Windows hosts.

It is worth setting up if you run coding agents natively on Windows and want to eliminate broken tool calls caused by the model's poor PowerShell generation. The main catch is the restricted surface area: with only 109 translated commands, complex shell scripts, unmapped flags, or heavy interactive tools will fail and still require a full Linux environment.

more: https://github.com/20000419/fauxnix

zvec-grep is a local-first command line tool that unifies ripgrep, BM25, and vector search into a single interface. Requiring Node.js 22 or newer, it stores local indexes in a hidden directory and runs embedding generation on your own machine. It is designed to be called directly by humans in the terminal or invoked automatically by local coding agents.

It is worth trying if you are tired of switching between grep and separate vector databases for agent workflows. The catch is that setting up local embeddings adds another moving part to your shell scripts, and the Node.js implementation sits alongside an experimental Rust version. Skip it if standard ripgrep already handles your codebase searches.

more: https://github.com/zvec-ai/zvec-grep

totec448-spec/chat-on-steroids is an open-source workspace that connects ChatGPT to local files, terminals, and testing tools via MCP and a browser extension. It runs on Windows, macOS, and Linux, letting multiple background workers edit code and run tests simultaneously while sharing your standard ChatGPT conversation limits. The system relies on your existing ChatGPT account and developer mode rather than invoking an independent API directly.

If you routinely juggle multiple terminal windows and want a local orchestrator to handle multi-file edits through your browser session, it saves manual context switching. The catch is that it is an unsigned beta touching your local shell with user-level privileges, and it sits precariously on top of OpenAI browser automation that could break with any interface update. Skip it if you require stable enterprise tooling or want to avoid juggling local security permissions for an unverified desktop app.

more: https://github.com/totec448-spec/chat-on-steroids