I'm Patrick Hughes. I build small AI tools for developers shipping agents into the real world. AgentGuard is the flagship: budget caps, loop detection, timeouts, and kill switches before your agent burns money at 2 AM.
$ pip install agentguard47Observed package downloads from PyPI, updated hourly. Counts include mirror noise filtered out where the upstream supports it. Downloads are a usage signal, not an adoption proof. A conservative floor is shown when every upstream is unavailable.
The bet: a useful software company can be one human, a stack of tools, and agents doing the boring work.
Most agent tools tell you what happened after the run. AgentGuard is the guardrail layer I wanted before letting agents work unattended.
Start with the Python SDK. Add MCP only when you want your coding agent to read traces and budget health. Use the hosted dashboard when local files are not enough.
Observed package downloads from PyPI, updated hourly. Counts include mirror noise filtered out where the upstream supports it. Downloads are a usage signal, not an adoption proof. A conservative floor is shown when every upstream is unavailable.
from agentguard import BudgetGuard, JsonlFileSink, LoopGuard, Tracer
budget = BudgetGuard(max_cost_usd=5.00, max_calls=50)
loop = LoopGuard(max_repeats=3)
tracer = Tracer(
sink=JsonlFileSink(".agentguard/traces.jsonl"),
service="support-agent",
guards=[loop],
)
with tracer.trace("agent.run") as span:
budget.consume(calls=1, cost_usd=0.02)
loop.check("search", {"query": "refund policy"})
span.event("tool.call", data={"tool": "search"})
# Call your agent or tool here.Open source. Local-first. Raises inside the running process when a budget, loop, rate, retry, or timeout limit is crossed.
Read-only access for Claude Code, Cursor, Codex, and other MCP clients to traces, alerts, usage, costs, and budget health.
Use the hosted app for read keys, retained history, alerts, and shared visibility. Keep the first integration local if that is all you need.
Create read key ->Stop a run before an experiment turns into a surprise bill.
Kill repeated tool calls before retries become an operator problem.
Put a hard wall-clock ceiling around unattended agent work.
Keep background jobs from hammering tools while nobody is watching.
Stop retry storms instead of letting flaky tools spin forever.
Write JSONL traces and incident reports without sending data anywhere.
{
"mcpServers": {
"agentguard": {
"command": "npx",
"args": ["-y", "@agentguard47/mcp-server"],
"env": {
"AGENTGUARD_API_KEY": "ag_your_read_key_here"
}
}
}
}Use AgentGuard when you need runtime controls. The other tools are small utilities from the same workshop. Open what helps. Skip what does not.
$ pip install agentguard47Runtime guardrails for AI agents before they spend money unattended.
$ pip install agentguard47Estimate local LLM memory, GPU layers, and CPU offload risk.
Rank local LLMs for your GPU, workload, and speed-quality tradeoff.
Compare GGUF quant levels by size, quality, speed, and GPU fit.
Unlimited local LLM runs, saved rigs, model import, and history.
Describe an agent. Get risks, architecture, guardrails, and next steps.
Watch multi-agent coordination, handoffs, and tool calls in real time.
Paste a URL. Get a summary, key points, and sentiment in seconds.
Four AI personas that react to your live podcast in real time.
Persistent key-value memory for AI agents, paid per call with x402.
This is not a platform committee. It is Patrick building useful AI tools, using AgentGuard on the agent work that should not run loose.
AgentGuard is the product I reach for before an agent can spend, loop, or run unattended.
22 small agents handle repeatable work: checks, summaries, drafts, and repo chores.
Every useful lesson turns into docs, posts, examples, or another small tool.
Patrick keeps the judgment. The software handles the boring loops around it.
Short posts on agents, local models, cost control, and the parts of this stack that actually held up.
As the AI world heats up, learn how to build AI agents that prioritize user control and transparency. Discover practical strategies for creating observable and accountable automation on your own hardware.
In the new era of AI, simply building smart agents isn't enough. Discover how to architect automated systems for true accountability, user trust, and ethical operation, empowering local AI developers.
As the AI industry heats up with legal battles and ethical debates, discover how to engineer AI agents that prioritize user control, privacy, and adaptability, ensuring they remain valuable on your hardware.
Tom Tunguz called it localmaxxing. I run a 3070 + 5070 Ti + 5090 in one box and serve Llama 3.1 8B locally every day. Here are the real tokens-per-second, the real watts, and the real cost per million tokens.