<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Claude on Devops Monk</title><link>https://blog.devops-monk.com/tags/claude/</link><description>Recent content in Claude on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 17 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.devops-monk.com/tags/claude/index.xml" rel="self" type="application/rss+xml"/><item><title>Claude Code Plugins: The Complete Guide to Building and Sharing Extensions</title><link>https://blog.devops-monk.com/2026/05/claude-code-plugins-guide/</link><pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/claude-code-plugins-guide/</guid><description>Skills, agents, and hooks you add to .claude/ are powerful — but they are locked to one project. Every time you start a new repo you copy the same files, maintain them in multiple places, and drift out of sync. Claude Code plugins solve this: a plugin is a shareable, versioned package that carries all your customisations and can be installed in any project with one command.
This post covers what plugins are, when to use them, and how to build a real one from scratch — a DevOps helper that ships a deployment skill, a pre-deploy safety hook, and an MCP server connection to your Kubernetes cluster.</description></item><item><title>Claude Extended and Adaptive Thinking: Making Claude Reason Before It Answers</title><link>https://blog.devops-monk.com/2026/05/claude-adaptive-thinking-guide/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/claude-adaptive-thinking-guide/</guid><description>By default, Claude generates its response token by token without any deliberate planning step. For most tasks — answering a question, writing a function, explaining a concept — this is fine. The response comes quickly and it is good.
For some tasks, it is not enough. Complex multi-step reasoning problems, ambiguous architecture decisions, intricate security analyses — these benefit from Claude thinking through the problem before committing to an answer. That is what extended thinking and adaptive thinking provide.</description></item><item><title>Claude Managed Agents: Deploy AI Agents Without Managing Infrastructure</title><link>https://blog.devops-monk.com/2026/05/claude-managed-agents-guide/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/claude-managed-agents-guide/</guid><description>Building an AI agent that runs autonomously — browses the web, executes code, reads and writes files, persists memory across sessions — requires infrastructure. You need a sandbox, a process that can run for hours without your web server timing out, and a way to resume from where you left off after a network hiccup.
Claude Managed Agents, launched in public beta in April 2026, offloads all of that to Anthropic.</description></item><item><title>Claude Models in 2026: Opus, Sonnet, and Haiku Compared</title><link>https://blog.devops-monk.com/2026/05/claude-models-guide-2026/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/claude-models-guide-2026/</guid><description>Picking the wrong Claude model is expensive. Opus on every task costs 5x more than Sonnet for comparable results on most work. Haiku on a complex reasoning task produces worse output than just asking Sonnet. And if you are still using models from early 2025, some of them are deprecated — or will be soon.
This guide covers every current Claude model, what each is good at, how much they cost, and a concrete decision framework for choosing the right one.</description></item><item><title>Claude Prompt Caching: Cut Your API Costs by 90%</title><link>https://blog.devops-monk.com/2026/05/claude-prompt-caching-guide/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/claude-prompt-caching-guide/</guid><description>If you are calling the Claude API repeatedly with a large system prompt, a big document, or a long codebase context — and you are not using prompt caching — you are paying full price every time for content that has not changed. Prompt caching stores a prefix of your prompt server-side and charges 90% less to read it back on every subsequent request.
For applications that repeatedly process the same context, this is the single highest-impact API optimisation available.</description></item><item><title>Spring AI 2.0: Build a RAG Application with Spring Boot</title><link>https://blog.devops-monk.com/2026/05/spring-ai-rag-application/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/05/spring-ai-rag-application/</guid><description>Spring AI 1.0 GA shipped in May 2025. It brings the Spring programming model to AI development: a unified ChatClient API that works across Claude, OpenAI, Gemini, Ollama, and Azure OpenAI — switching AI providers is changing one dependency.
This guide builds a complete RAG (Retrieval-Augmented Generation) application that answers questions about your documentation using any AI provider.
What Is RAG? A large language model (LLM) knows everything in its training data but nothing about your specific documents, code, or business data.</description></item><item><title>Building a Personal AI Assistant with Claude Agent SDK and Bun</title><link>https://blog.devops-monk.com/2026/04/building-personal-ai-assistant-claude/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/building-personal-ai-assistant-claude/</guid><description>Most AI assistants are chatbots. You ask, they answer, the interaction ends. The interesting shift happening right now is treating AI as an autonomous worker — something that runs on a schedule, produces real artifacts, and delivers results without you being in the loop.
This post walks through building that kind of assistant: a background agent that runs weekly, researches a set of topics relevant to your work, and delivers a structured briefing via Telegram or email.</description></item><item><title>Claude Code as a Security Scanner: Beyond Pattern Matching</title><link>https://blog.devops-monk.com/2026/04/claude-code-security-scanner/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/claude-code-security-scanner/</guid><description>Tools like ESLint, Semgrep, and Bandit catch what they are programmed to find: known patterns, common injection strings, deprecated API calls. They are fast, reliable, and deterministic. They are also blind to anything that requires understanding what your code is supposed to do.
Claude Code operates differently. It reads code the way a human security researcher would — tracing data flows across files, understanding business logic, and reasoning about what could go wrong given the specific context of your application.</description></item><item><title>Claude Code Hooks, Commands, Skills, and Subagents: The Complete Guide</title><link>https://blog.devops-monk.com/2026/04/claude-code-hooks-subagents-piping/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/claude-code-hooks-subagents-piping/</guid><description>Most teams use Claude Code reactively — they type a prompt, Claude responds, they type another. That is fine, but it leaves significant value on the table. Claude Code has four automation layers that let you turn it from a reactive assistant into an active workflow participant:
Layer What it does When to reach for it Hooks Shell or HTTP calls that fire on lifecycle events &amp;ldquo;This must happen every time, without exception&amp;rdquo; Custom Commands Reusable slash commands for repeatable prompts &amp;ldquo;I type the same prompt repeatedly&amp;rdquo; Skills Context-aware instructions Claude loads automatically &amp;ldquo;Claude should always do X when working on Y&amp;rdquo; Subagents Separate Claude instances for isolated, parallel work &amp;ldquo;This task is noisy and the main session only needs a summary&amp;rdquo; This post covers how to create each one and when to use them.</description></item><item><title>Claude Computer Use for DevOps: When to Use It and When to Use an API</title><link>https://blog.devops-monk.com/2026/04/claude-computer-use-devops-workflows/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/claude-computer-use-devops-workflows/</guid><description>Claude&amp;rsquo;s computer use capability — the ability to see your screen and interact with applications via mouse clicks, keyboard input, and scrolling — is one of the most discussed features in the AI space. It is also one of the most misapplied.
The correct mental model is not &amp;ldquo;Claude can now automate everything on my screen.&amp;rdquo; It is &amp;ldquo;Claude now has a flexible fallback layer for tasks that do not have a structured API integration.</description></item><item><title>Mastering Claude Code CLI: The Complete Guide for DevOps Engineers</title><link>https://blog.devops-monk.com/2026/04/mastering-claude-code-cli/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/mastering-claude-code-cli/</guid><description>If you have been using Claude in a browser tab to help with code, you are leaving most of its capability on the table. Claude Code CLI brings the full power of Claude directly into your terminal — it reads your actual codebase, runs real commands, edits files, commits code, and integrates with every tool in your DevOps stack. This guide covers everything from installation to advanced patterns that most engineers never discover.</description></item><item><title>MCP Servers Worth Installing: For Developers, Testers, and DevOps Teams</title><link>https://blog.devops-monk.com/2026/04/mcp-servers-for-devops-teams/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/mcp-servers-for-devops-teams/</guid><description>The MCP (Model Context Protocol) ecosystem now has over 14,000 servers. Most of them you do not need. Installing too many slows responses, inflates your context window with tool definitions that never get used, and turns debugging into a guessing game across a dozen integrations.
This guide applies a simple filter: only install a server if it replaces a daily copy-paste workflow. It is organised by role — developers, QA testers, and DevOps/platform engineers — because the right stack is different for each.</description></item><item><title>Stop Burning Tokens: A Practical Guide to Claude Code Cost Optimization</title><link>https://blog.devops-monk.com/2026/04/claude-code-token-optimization/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/claude-code-token-optimization/</guid><description>Token usage with Claude Code follows a frustrating pattern: costs are not spread evenly — they cluster around a handful of bad habits. Most developers using Claude Code daily are burning 40–60% more tokens than they need to, simply because of how they phrase prompts, what they put in CLAUDE.md, and which model they reach for by default.
This guide covers five concrete changes that make an immediate difference.
Why Tokens Are Worth Caring About Every message you send in a Claude Code session includes:</description></item><item><title>The Claude Code /loop Command: In-Session Automation Explained</title><link>https://blog.devops-monk.com/2026/04/claude-code-loop-command/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/claude-code-loop-command/</guid><description>The /loop command in Claude Code lets you schedule a prompt to repeat at a regular interval within an active session. It is one of the less-documented features, and it is also one of the most misunderstood — particularly around what it cannot do.
This post explains what /loop actually is, the three scenarios where it genuinely earns its keep, and where cron jobs remain the better choice.
What /loop Does /loop 5m check if the Vite dev server is still running and report any new errors This runs the prompt immediately, then repeats it every 5 minutes for the duration of your session.</description></item><item><title>Writing a CLAUDE.md That Actually Works</title><link>https://blog.devops-monk.com/2026/04/writing-claude-md-that-works/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/writing-claude-md-that-works/</guid><description>Every CLAUDE.md file gets loaded into context on every session. Most teams treat it like documentation — a place to describe the project, list the tech stack, explain what the tests do. That is the wrong mental model and it is why most CLAUDE.md files are both too long and too ineffective.
CLAUDE.md is behavioral programming. Its job is to change how Claude makes decisions, not to describe facts that Claude can read from the codebase itself.</description></item><item><title>You Don't Need a Framework to Build an AI Assistant</title><link>https://blog.devops-monk.com/2026/04/build-ai-assistant-without-framework/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/2026/04/build-ai-assistant-without-framework/</guid><description>There is a tendency in the AI tooling space to reach for frameworks — LangChain, AutoGen, CrewAI, OpenClaw — the moment you want an AI that does more than answer one question at a time. Most of the time, that is the wrong move. The framework adds complexity, dependencies, and debugging surface area for problems that a few shell scripts and cron jobs solve perfectly well.
Claude Code&amp;rsquo;s headless mode (-p flag) plus a markdown file for personality plus cron scheduling is a complete AI assistant stack.</description></item></channel></rss>