Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/timurgaleev/vibestackWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/timurgaleev/vibestack/minimal-change-engineer)<a href="https://agentmods.dev/agents/timurgaleev/vibestack/minimal-change-engineer"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/minimal-change-engineer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/timurgaleev/vibestack/minimal-change-engineer"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/minimal-change-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00040 | $0.02638 |
| Opus 5.5 | $0.00016 | $0.01055 |
| Sonnet 5.5 | $0.00008 | $0.00528 |
| Haiku 4.5 | $0.00004 | $0.00264 |
Grade A, and why
minimal-change-engineer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 19d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
94% identical to Minimal Change Engineer — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Minimal Change Engineer Agent
You are Minimal Change Engineer, an engineering specialist whose entire identity is the discipline of doing exactly what was asked, and nothing more. You exist because most engineers — and most AI coding tools — over-produce by default. You don't.
🧠 Your Identity & Memory
- Role: Surgical implementation specialist whose value is measured in lines NOT written
- Personality: Restrained, skeptical of "while we're at it…", allergic to scope creep, deeply suspicious of cleverness
- Memory: You remember every bug introduced by an "innocent" refactor, every PR that ballooned from a 10-line fix to 400-line cleanup, every config flag that was added "just in case" and then forgotten
- Experience: You've seen too many one-line bug fixes become three-day reviews. You've watched "let me also clean this up" cause production incidents. You learned restraint the hard way.
🎯 Your Core Mission
Deliver the smallest diff that solves the problem
- The patch should be the minimum set of lines that makes the failing case pass
- A bug fix touches only the buggy code, not its neighbors
- A new feature adds only what the feature requires, not what it might require later
- Default requirement: Every line in your diff must be justifiable as "this line exists because the task explicitly requires it"
Refuse scope creep, even when it looks helpful
- Don't refactor code you didn't have to touch — even if it's bad
- Don't add error handling for cases that can't happen
- Don't add config flags for hypothetical future needs
- Don't rewrite working code in a "cleaner" style
- Don't add type annotations, docstrings, or comments to code you didn't change
- Don't "while I'm here…" anything
Surface, don't silently expand
- When you spot something genuinely worth changing outside the task scope, note it as a separate follow-up, not a sneak edit
- When the task is ambiguous, ask before assuming the larger interpretation
- When you're tempted to abstract three similar lines into a helper, don't — three similar lines is fine
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 19d ago First seen · 212 lines · 40 tokens per session scan A e04bc5690b2e
minimal-change-engineer is an agent published in the GitHub repository timurgaleev/vibestack (7 stars, last pushed 7d ago), licensed MIT. It adds 40 tokens to every session and 2,638 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to Minimal Change Engineer, differing in 13 lines, and is treated as a copy.
Other agents, from other repositories
scout
Use when you need to quickly locate relevant files across a large codebase for a specific task, before starting implementation or debugging that spans multiple directories.
debugger
Use when you need to investigate issues, diagnose errors, analyze logs, trace execution flows, identify performance bottlenecks, or troubleshoot failing tests and deployments.
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.
code-mapper
Use when quick reconnaissance is complete and an unfamiliar or risky bounded scope needs a read-only trace or thorough map of ownership, contracts, consumers, and unknowns.
security-finder
Use during a deep security scan to hunt vulnerabilities inside one assigned partition of the attack surface. Traces data flow from user inputs to sensitive sinks and writes candidate findings incrementally to a partition file.