MCP tool poisoning: approving a server once isn't approving it forever
MCP tool poisoning hides inside a server's tool descriptions. How the rug pull variant works, and a hash check that catches when a trusted tool quietly changes.
MCP tool poisoning hides inside a server's tool descriptions. How the rug pull variant works, and a hash check that catches when a trusted tool quietly changes.
How git worktrees let multiple Claude Code sessions work on the same repo at once, and the gotchas: shared stash stacks, detached HEAD, and branch locks.
Building a custom Claude Code status line in bash: the stdin JSON contract, caching slow checks, Docker health over SSH, and bash 3.2 compatibility quirks.
A dry-run daily job that asks an LLM whether a domain seen by AdGuard Home or privoxy looks like an ad or tracker, before any blocklist ever gets touched.
How I wrapped a self-hosted Omada network controller's undocumented REST API in a shell script and turned it into a Claude Code agent for daily network checks.
Why I dropped Anthropic's Managed Agents product for this blog's post pipeline and moved to a Claude Code scheduled cloud routine on my existing Team plan.
AI coding agent setups drift like code but have no test suite. Ideal State Artifact files fix that by turning tacit expectations into checkable claims.
One CLI for all Google Workspace APIs, JSON output, bash-friendly. Here's how I replaced two MCP servers with gws and what it means for AI agent workflows.
How I built a nightly pipeline that compiles raw Claude Code session logs into structured knowledge articles, stored in pgvector and mirrored to Obsidian.
How Claude Code skills and agents turn repetitive work into reusable workflows. 19 agents, automatic skill loading, and real examples.
Anthropic's skills repo is now public on GitHub. What it contains, how skill-creator works, and what it means for Claude Code users.
How I use Claude Code hooks to block dangerous commands, scan for secrets, inject context, and get Telegram notifications when something needs attention.
Eight slash commands for Toggl time tracking: some trivially simple, one genuinely useful, and what that says about automation ROI.
Eleven slash commands for deployments, diagnostics, and system health — and how they compare to the runbook documents they replaced.
How Claude Code slash commands work: file structure, $ARGUMENTS, frontmatter, namespacing, and the patterns that make them useful.
MCP is an open protocol that lets AI assistants talk to external tools and data sources. Here is how it works and how to configure it in Claude Code.
48 commands, 18 agents, 22 rules, 11 hooks. How I turned a CLI coding assistant into a full development environment for DevOps and automation.
Running 5 parallel research agents to audit my Claude Code workbench: what the latest AI engineering research says, what I already had, and what was actually new.
How I built a local multimodal RAG with pgvector, Gemini embeddings, and an MCP server so Claude Code can search past sessions and internal docs on demand.
Claude Code ecosystem growing fast, MCP security under scrutiny, multi-agent orchestration going mainstream. Weekly roundup of what caught my eye.