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 alertsgit 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/alerts)<a href="https://agentmods.dev/skills/kilo-org/kilo-marketplace/alerts"><img src="https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/alerts/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/alerts"><img src="https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/alerts.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.00056 | $0.00689 |
| Opus 5 | $0.00028 | $0.00345 |
| Sonnet 5 | $0.00011 | $0.00138 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
newrelic-cli-alerts 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alert Management
Manage alert policies, conditions, and notification channels via CLI.
List Alert Policies
newrelic alerts policy list
Get a Policy
newrelic alerts policy get --policyId <ID>
Create a Policy
newrelic alerts policy create \
--name "My App - Performance" \
--incidentPreference "PER_CONDITION_AND_TARGET"
Incident preference options:
PER_POLICY— one incident per policy breachPER_CONDITION— one incident per conditionPER_CONDITION_AND_TARGET— most granular, one per condition+entity
Alert Conditions
List Conditions for a Policy
newrelic alerts conditions list --policyId <POLICY_ID>
Create an APM Metric Condition
newrelic alerts apmCondition create \
--policyId <POLICY_ID> \
--name "High Response Time" \
--type "apm_app_metric" \
--metric "response_time_web" \
--conditionScope "application" \
--violationCloseTimer 24 \
--threshold 2.0 \
--thresholdDuration 5 \
--thresholdOccurrences "ALL"
Delete a Condition
newrelic alerts conditions delete --conditionId <ID>
NRQL Alert Conditions
newrelic alerts nrqlCondition static create \
--policyId <POLICY_ID> \
--name "Error Rate > 5%" \
--query "SELECT percentage(count(*), WHERE error IS true) FROM Transaction WHERE appName='my-app'" \
--threshold 5 \
--thresholdDuration 5 \
--thresholdOccurrences "ALL" \
--violationTimeLimitSeconds 86400
Notification Channels
# List channels
newrelic alerts channel list
# Create email channel
newrelic alerts channel create \
--name "On-Call Email" \
--type email \
--configuration '{"recipients": "[email protected]", "include_json_attachment": false}'
View Open Incidents
newrelic nrql query --accountId $NEW_RELIC_ACCOUNT_ID --query "
SELECT *
FROM NrAiIncident
WHERE event = 'open'
SINCE 24 hours ago
LIMIT 20
"
Check Entity Alert Severity
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 · 128 lines · 56 tokens per session scan A 5c2408f8ce73
newrelic-cli-alerts is a skill published in the GitHub repository Kilo-Org/kilo-marketplace (175 stars, last pushed 22d ago), licensed Apache-2.0. It adds 56 tokens to every session and 689 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…