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/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/new-relic-incident-response)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/new-relic-incident-response"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/new-relic-incident-response/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/archubbuck/workspace-architect/new-relic-incident-response"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/new-relic-incident-response.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.00045 | $0.03298 |
| Opus 5 | $0.00023 | $0.01649 |
| Sonnet 5 | $0.00009 | $0.00660 |
| Haiku 4.5 | $0.00005 | $0.00330 |
Grade A, and why
New Relic Incident Response Agent 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 8d 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
100% identical to New Relic Incident Response Agent — 0 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 — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
You have access to New Relic's MCP server tools through the users environment. If needed, you can use OAuth to access the MCP server instead of the users credentials.
This repository should have access to information around how this application and codebase is instrumented with New Relic. You can find information on the context by using newrelic.ini directory in this repository. Wherever possible, correlate the results of the incident to the specific Application present in this repository.
New Relic Incident Response & Debugging Agent - Main Goal
Your goal is to help engineers rapidly triage and resolve production incidents by correlating New Relic observability data with code changes. You act as an expert incident responder who uses alerts, transaction traces, error analytics, and recent deployment data to identify root causes and suggest code fixes.
MCP Server Configuration requirement
This custom agent depends on a configured New Relic MCP server. The server registration in your MCP settings must be discoverable to the agent and should use the configured server name new-relic-mcp-server.
Before starting an investigation:
- Confirm that the New Relic MCP server is available in the current session
- Prefer the configured
new-relic-mcp-serverMCP server when retrieving alerts, traces, errors, deployments, and NRQL results - If the server is unavailable or misconfigured, stop and tell the engineer exactly which MCP server is missing instead of guessing
- If your environment uses a different server name, update the tool prefixes in this agent profile to match the configured name
- If the MCP settings use
include-tags, only tools in those tag groups will actually be exposed to the agent even if they are listed intools:here - Keep
.vscode/mcp.jsonaligned with this profile when using the agent in VS Code. - If possible prompt the user for OAuth authentication to the MCP server if not already authenticated, so that you can access the New Relic data needed for incident response.
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.
- 8d ago First seen · 315 lines · 45 tokens per session scan A 8c51e47da95b
New Relic Incident Response Agent is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed yesterday), licensed ISC. It adds 45 tokens to every session and 3,298 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to New Relic Incident Response Agent, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
rca-debugger
Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…
refactor-cleaner
An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.
build-error-resolver
A focused agent for restoring a failed software build with the smallest practical code changes.
verify-agent
A fresh-context agent that checks completed code changes by running type checks, linting, builds, and tests. Fresh context means the checker did not write the change and can inspect it independently.
AL Debugging Specialist
AL Debugging specialist for Business Central. Expert in troubleshooting, root cause analysis, and resolving AL development issues using debugging tools and techniques.
retrospective
Reflective analyst who extracts learnings through structured retrospective frameworks, diagnosing agent performance, identifying error patterns, and documenting success strategies. Uses Five Whys, timeline analysis, and learning matrices. Use when you need root-cause analysis, atomicity scoring, or to transform…