[jcountsNR]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• I have read and followed the Guidance for submissions involving paid services.
• My contribution adds a new instruction, prompt, agent, skill, workflow, or canvas extension file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, workflow, or canvas extension with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.
• I am targeting the main branch for this pull request.

---

Description

Summary

• Align New Relic APM, FinOps, Kubernetes, and incident-response agents with current Copilot models and New Relic MCP tools.
• Replace generic APM guidance with a focused New Relic investigation workflow.
• Remove the duplicate generic New Relic MCP agent and prompt-secrecy boilerplate.
• Clarify that CloudCostV2Test is an example test dataset, not a universal production event type.
• Regenerate the agent README.

Validation

• npm run build passed.
• Diagnostics passed for all four New Relic agents.
• git diff --check passed.

Copilot Testing

Live testing with a configured New Relic MCP server was not performed. Before merge, select each agent in Copilot and verify its tools and a representative read-only query against a test account.

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• New canvas extension.
• Update to existing instruction, prompt, agent, plugin, skill, workflow, or canvas extension.
• Other (please specify):

---

Additional Notes

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[github-actions]

🔒 PR Risk Scan Results

Scanned 4 changed file(s).

Severity	Count
🔴 High	0
🟠 Medium	0
ℹ️ Info	0

✅ No matching risk patterns were detected in changed files.

This is an automated soft-gate report. Findings indicate review targets and do not block merge by themselves.

[github-actions]

🔍 Vally Lint Results

⚠️ Warnings or advisories found

Scope	Checked
Skills	0
Agents	4
Total	4

Severity	Count
❌ Errors	0
⚠️ Warnings	0
ℹ️ Advisories	1

Summary

Level	Finding
ℹ️	Vally currently lints SKILL.md content. Agent files were detected but skipped:

Full linter output

### Agent files detected (not linted by vally)
ℹ️ Vally currently lints SKILL.md content. Agent files were detected but skipped:
agents/new-relic-apm.agent.md
agents/new-relic-finops.agent.md
agents/new-relic-incident-response.agent.md
agents/new-relic-kubernetes.agent.md

[github-actions]

🚦 Submission status: 👀 Ready for review

Risk tier: merge-risk:medium — New or substantially changed resource without privileged execution
Required to merge: passing submission-gate checks plus 1 approval from reviewers with write access.

Why this tier

• Adds 3 file(s), e.g. agents/new-relic-apm.agent.md
• Changes 668 lines (low-risk limit is 40)

Automated checks

Check	Status	Details
Line endings	✅ Passed	Passed · logs
Spelling	✅ Passed	Passed · logs
Generated README consistency	✅ Passed	Passed · logs
Skill lint (vally)	✅ Passed	Passed · logs
Risk scan	✅ Passed	Passed · logs
Contributor reputation	✅ Passed	Passed · logs
Duplicate resource scan	⚠️ Failed (advisory, non-blocking)	The workflow did not complete successfully · logs
PR quality signal	⏭️ Skipped	Skipped by its workflow · logs

Action needed

• ⚠️ Advisory checks did not complete (Duplicate resource scan). This does not block the PR.

Review

• Approvals: 0/1
• Assigned reviewer: not assigned yet — comment /request-review to ask for one
• Review target date: not set
• Still needed: 1 more approval(s)
• No staffed reviewer pool owns these files yet; any reviewer with write access counts as the domain reviewer.

Commands

Command	Who	What it does
/rerun-checks	PR author, maintainers	Re-runs failed or incomplete checks and re-evaluates this gate
/request-review	PR author, maintainers	Asks the review rotation to assign a reviewer (adds needs-reviewer)

_{Updated for 6744659 · gate run · This comment is maintained automatically — see submission gate docs.}

[jcountsNR]

Note that this is an update for PR#5174

[Copilot]

🟡 Changes recommended

The scalar tools declarations cause tools.forEach to throw a TypeError, blocking website metadata generation.

5 open issues

• Declare tools as a YAML sequence · New
• Remove unsupported ORDER BY from the faceted aggregate · New
• Detect restart increases, not cumulative restart counts · New
• Filter pod events and logs by namespace · New
• Remove non-aggregated nodeName from the SELECT · New

What changed in this PR

Expands the New Relic agent collection with focused APM, FinOps, and Kubernetes investigation workflows and updates the existing incident-response agent.

Changes:

• Adds three agents with New Relic MCP guidance and domain-specific investigation examples.
• Updates model preferences across all four agents and clarifies the FinOps example dataset.
• Regenerates the agent catalog with descriptions and installation links.

File	Description
docs/​README.agents.md	Adds catalog entries for the three new agents.
agents/​new-relic-kubernetes.agent.md	Adds Kubernetes diagnostics and telemetry query examples.
agents/​new-relic-incident-response.agent.md	Updates model preferences.
agents/​new-relic-finops.agent.md	Adds cloud-cost analysis workflows and NRQL examples.
agents/​new-relic-apm.agent.md	Adds a focused application-performance investigation workflow.

_{Review effort: Balanced (auto)}

[Copilot]

🟡 Changes recommended

Scalar tools declarations in the FinOps and Kubernetes agent profiles cause tools.forEach(...) to throw, blocking website data generation and deployment.

2 open issues

• Declare tools as a YAML sequence · New
• Declare tools as a YAML sequence

2 previously missed issues

In code that hasn't changed since last review

Exclude succeeded Jobs from the pod readiness check

agents/​new-relic-kubernetes.agent.md:165

A successfully completed Job pod has status = 'Succeeded' and is no longer ready, so this predicate reports healthy completed work as unhealthy. In namespaces with many Jobs, those samples can also consume the 100-row limit and obscure actual failures. Exclude successful completion and apply the readiness check only to running pods.

Filter logs by namespace as well as pod

agents/​new-relic-kubernetes.agent.md:265

[P2] Include the namespace in this log filter. Pod names are unique only within a namespace: two namespaces can both contain a StatefulSet pod named redis-0. Filtering only by cluster and pod then mixes their logs, allowing errors from an unrelated workload to be attributed to the investigated pod. Use the namespace established in Step 1.

4 resolved since last review

• Remove non-aggregated nodeName from the SELECT
• Filter pod events and logs by namespace
• Detect restart increases, not cumulative restart counts
• Remove unsupported ORDER BY from the faceted aggregate

_{Review effort: Balanced (auto)}

[Copilot]

🔵 Needs a closer look

Unresolved query errors can break the cost breakdown, falsely flag completed pods or historical restarts as active problems, and mix logs across namespaces.

1 open issue

• Declare tools as a YAML sequence

3 previously missed issues

In code that hasn't changed since last review

Remove unsupported standalone ORDER BY from faceted query

agents/​new-relic-finops.agent.md:188

This is a standalone row-level ORDER BY, which the NRQL reference says does not apply to FACET queries. It is not the FACET ... ORDER BY modifier either, which must immediately follow the facet and use an aggregate function. Remove this unsupported clause; the first selected sum() already ranks facets descending, so LIMIT 10 gives the requested top ten services.

Exclude successfully completed pods from unhealthy pod detection

agents/​new-relic-kubernetes.agent.md:165

Successful Job/CronJob pods normally have status = 'Succeeded' and are not Ready, so this predicate reports ordinary completed jobs as unhealthy pods. Exclude successful terminal pods before applying the status/readiness check to avoid false incident candidates in namespaces with batch workloads.

Include namespace when querying pod logs

agents/​new-relic-kubernetes.agent.md:265

Pod names are unique only within a namespace. For example, two namespaces can both contain a StatefulSet pod named api-0, so this query combines their logs despite the namespace scoped in investigation step 1. Include namespace_name to avoid diagnosing the selected workload using another namespace's errors.

1 resolved since last review

• Declare tools as a YAML sequence

_{Review effort: Balanced (auto)}

[Copilot]

🟡 Changes recommended

The agent examples contain invalid NRQL and filtering errors that can cause query failures, false Kubernetes incidents, misattributed logs, and incomplete cost results.

5 open issues

• Declare tools as a YAML sequence
• Match both supported is_k8s values · New
• Exclude successfully completed Job and CronJob pods · New
• Scope pod log queries by namespace · New
• Separate pod lifetimes and handle restart-counter resets · New

_{Review effort: Balanced (auto)}