newrelic-cli-deployments

newrelic-cli-deployments is a skill for Claude Code, Codex from Kilo-Org/kilo-marketplace. It costs 52 tokens per session (682 once invoked), scanned A, original, Apache-2.0.

A set of New Relic CLI procedures for recording and reviewing deployment markers. These markers are release events shown alongside performance data so changes can be compared with later behaviour.

In plain words
What is it for?
Use it to create deployment records, list recent releases, and add deployment tracking to GitHub or GitLab CI pipelines.
Why use it?
It helps connect a performance change to the release that may have caused it.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create deployment records, list recent releases, and add deployment tracking to GitHub or GitLab CI pipelines.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kilo-org/kilo-marketplace/deployments
Install

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.

Any agent
npx skills add Kilo-Org/kilo-marketplace --skill deployments
Clone the repo
git clone --depth 1 https://github.com/Kilo-Org/kilo-marketplace

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for newrelic-cli-deployments

README.md
[![agentmods](https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/deployments/github.svg)](https://agentmods.dev/skills/kilo-org/kilo-marketplace/deployments)
Your own site
<a href="https://agentmods.dev/skills/kilo-org/kilo-marketplace/deployments"><img src="https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/deployments/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.

agentmods 80×15 button for newrelic-cli-deployments

Your own site · 80×15
<a href="https://agentmods.dev/skills/kilo-org/kilo-marketplace/deployments"><img src="https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/deployments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 682 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.00682
Opus 5 $0.00026 $0.00341
Sonnet 5 $0.00010 $0.00136
Haiku 4.5 $0.00005 $0.00068

Measured 9d ago against content hash 9914abcfbaa5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

newrelic-cli-deployments 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.

skills/newrelic-cli-skills/deployments/SKILL.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deployment Markers

Record deployment events in New Relic so you can correlate releases with performance changes.


Record a Deployment

newrelic apm deployment create \
  --applicationId <APP_ID> \
  --revision "v1.2.3" \
  --description "Brief description of what changed" \
  --user "deploy-bot"

Required

  • --applicationId — numeric APM application ID
  • --revision — version string (e.g. git SHA, semver, MR number)

Optional

  • --description — what changed (show in NR UI on charts)
  • --user — who/what deployed
  • --changelog — detailed change notes

Get Application ID

newrelic entity search --name "my-app" --type APPLICATION --domain APM | \
  jq '.[] | {name, applicationId}'

List Recent Deployments

newrelic apm deployment list --applicationId <APP_ID>

GitLab/GitHub CI Integration

Add to your CI pipeline after a successful deploy:

#!/bin/bash
# deploy-marker.sh
APP_ID="${NEW_RELIC_APP_ID}"
REVISION="${CI_COMMIT_SHORT_SHA:-$(git rev-parse --short HEAD)}"
DESCRIPTION="${CI_COMMIT_TITLE:-Deployment}"
USER="${GITLAB_USER_LOGIN:-ci-bot}"

newrelic apm deployment create \
  --applicationId "$APP_ID" \
  --revision "$REVISION" \
  --description "$DESCRIPTION" \
  --user "$USER"

Why Deployment Markers Matter

After recording a deployment, the New Relic UI places a vertical line on all APM charts at that timestamp. This makes it immediately obvious if:

  • Response times increased after a deploy
  • Error rates spiked post-release
  • Throughput dropped unexpectedly

You can also query them via NRQL:

SELECT *
FROM Deployment
WHERE appId = <APP_ID>
SINCE 1 week ago

Automation: Mark on Every Merge

Script to call from a post-merge webhook or CI step:

#!/bin/bash
# Usage: ./deployment-marker.sh <app_id> <revision> <description>
set -euo pipefail

APP_ID="${1:?app_id required}"
REVISION="${2:?revision required}"
DESCRIPTION="${3:-Automated deployment}"

newrelic apm deployment create \
  --applicationId "$APP_ID" \
  --revision "$REVISION" \
  --description "$DESCRIPTION" \
  --user "ci-bot"

echo "Deployment marker recorded: $REVISION → app $APP_ID"

Read the full file on GitHub · 116 lines

Changes

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.

  1. 9d ago First seen · 116 lines · 52 tokens per session scan A 9914abcfbaa5

Subscribe to this mod's changes

newrelic-cli-deployments 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 682 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.

Related

Other skills, from other repositories

import-prom-rule

Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…

ccfos/nightingale · 125 tokens

chinese-git-workflow

A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.

jnMetaCode/superpowers-zh · 69 tokens

configure-env-variables

Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…

microsoft/power-platform-skills · 119 tokens

atmos-profiles

Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.

cloudposse/atmos · 35 tokens

managing-github-actions-secrets

Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.

PostHog/posthog-foss · 67 tokens

webhook-management

Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.

hoangsonww/Claude-Code-Agent-Monitor · 56 tokens