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.
npx skills add Kilo-Org/kilo-marketplace --skill diagnosticsgit clone --depth 1 https://github.com/Kilo-Org/kilo-marketplaceWrote 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/skills/kilo-org/kilo-marketplace/diagnostics)<a href="https://agentmods.dev/skills/kilo-org/kilo-marketplace/diagnostics"><img src="https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/diagnostics/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/skills/kilo-org/kilo-marketplace/diagnostics"><img src="https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/diagnostics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.00745 |
| Opus 5 | $0.00026 | $0.00373 |
| Sonnet 5 | $0.00010 | $0.00149 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
newrelic-cli-diagnostics 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Diagnostics
Validate New Relic agent configuration, connectivity, and reporting status.
Run Full Diagnostics
newrelic diagnose run
Checks: API key validity, account connectivity, agent config files, log paths, proxy settings.
Validate Config File
# For .NET agent on Windows
newrelic diagnose validate \
--config "C:\ProgramData\New Relic\.NET Agent\newrelic.config"
# For Linux
newrelic diagnose validate --config /etc/newrelic/newrelic.yml
Check Agent is Reporting
# Verify an app is actively sending data
newrelic nrql query --accountId $NEW_RELIC_ACCOUNT_ID --query "
SELECT count(*)
FROM Transaction
WHERE appName = 'my-app'
SINCE 10 minutes ago
"
# count = 0 means agent is not reporting
# Check entity reporting status
newrelic entity search --name "my-app" --type APPLICATION --domain APM | \
jq '.[] | {name, reporting}'
Check Agent Version
newrelic entity search --name "my-app" --type APPLICATION --domain APM | \
jq '.[] | {name, tags: (.tags[] | select(.key == "agentVersion"))}'
Connectivity Test
# Test API key and account access
newrelic profile list
newrelic nrql query --accountId $NEW_RELIC_ACCOUNT_ID \
--query "SELECT count(*) FROM NrIntegrationError SINCE 1 hour ago"
If NrIntegrationError count > 0, data ingestion has issues.
Common Issues
| Symptom | Likely Cause | Fix |
|---|---|---|
App shows reporting: false |
Agent stopped or config missing | Restart app pool / check agent logs |
| Transaction count = 0 | IIS app pool recycled without agent init | Ensure agent auto-instruments on startup |
High NrIntegrationError |
Data too large or malformed | Check agent logs for serialization errors |
alertSeverity: NOT_CONFIGURED |
No alert conditions on the entity | Add NRQL or APM metric conditions |
.NET Agent Specific (Windows/IIS)
# Check which apps are instrumented on a host
newrelic entity search --name "my-host" --type HOST | \
jq '.[] | .tags[] | select(.key == "apmApplicationNames")'
# Agent logs location (Windows)
# C:\ProgramData\New Relic\.NET Agent\Logs\
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.
- 9d ago First seen · 122 lines · 52 tokens per session scan A 578e0fe8715c
newrelic-cli-diagnostics is a skill published in the GitHub repository Kilo-Org/kilo-marketplace (175 stars, last pushed 22d ago), licensed Apache-2.0. It adds 52 tokens to every session and 745 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.