agentmods.dev

deploy-telemetry

deploy-telemetry is a skill for Claude Code, Codex from SkeneTechnologies/skene. It costs 47 tokens per session (669 once invoked), scanned A, original, MIT.

A setup workflow for Skene, a command-line system that builds analytics and event-tracking infrastructure. It verifies configuration and generated files before optionally sending them to Skene Cloud.

In plain words
What is it for?
Use it to build telemetry, check Skene configuration and migrations, create a feature registry, and push generated tracking data to Skene Cloud.
Why use it?
It provides checks and instructions for creating tracking artifacts and avoids inventing schemas when the command-line tool fails. Sending data to the cloud requires confirmation.

Skill for Claude CodeCodex

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

not rated 122repo +1 3d ago A scan 47 tokens original MIT

Good fit Use it to build telemetry, check Skene configuration and migrations, create a…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/skenetechnologies/skene/deploy-telemetry
View source ↗ SkeneTechnologies/skene pypi.org
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 SkeneTechnologies/skene --skill deploy-telemetry
Clone the repo
git clone --depth 1 https://github.com/SkeneTechnologies/skene

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 deploy-telemetry

README.md
[![agentmods](https://agentmods.dev/badge/skills/skenetechnologies/skene/deploy-telemetry.svg)](https://agentmods.dev/skills/skenetechnologies/skene/deploy-telemetry)
Your own site
<a href="https://agentmods.dev/skills/skenetechnologies/skene/deploy-telemetry"><img src="https://agentmods.dev/badge/skills/skenetechnologies/skene/deploy-telemetry.svg" alt="Measured on agentmods" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 669 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.
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.00047 $0.00669
Opus 5 $0.00023 $0.00334
Sonnet 5 $0.00009 $0.00134
Haiku 4.5 $0.00005 $0.00067

Measured 7d ago against content hash bcf8f520beed, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

deploy-telemetry 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 7d 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.

cursor-plugin/skills/deploy-telemetry/SKILL.md · 50 lines

How it starts

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

Deploy Telemetry

Set up analytics infrastructure via the Skene CLI.

Agent behavior rules

  • Autonomous. Run CLI commands, report results, suggest next step. No mid-flow questions except for genuine blockers.
  • CLI is the source of truth. Do NOT fabricate migration schemas or client code if the CLI fails.
  • User cannot type into agent terminals. Pipe safe defaults for routine prompts. Kill stuck terminals.
  • Upstream push can be a genuine blocker. Ask the user in chat to confirm before running uvx skene push — it POSTs skene-context/engine.yaml, {output_dir}/feature-registry.json when present, and the latest trigger migration to Skene Cloud (it does not generate SQL; run uvx skene build first if artifacts are missing).

Steps

  1. Discover CLI options Run uvx skene push --help to see available flags. Use only flags that appear in the output.

  2. Verify prerequisites

    • skene-context/engine.yaml must exist; trigger SQL lives under supabase/migrations/ as *_skene_triggers.sql after uvx skene build (older projects may use legacy *skene_trigger* / *skene_telemetry* filenames).
    • Feature registry: default skene-context/feature-registry.json (or {output_dir} from config; legacy skene/feature-registry.json auto-detected). If missing, push still runs but omits the registry until build creates it.
    • If engine or migrations are missing: tell the user to run uvx skene build first, then retry deploy.
    • ls supabase/ 2>/dev/null — if missing: "No Supabase directory. Set up Supabase first."

  3. Ask user to confirm Tell the user: "uvx skene push uploads engine, feature-registry.json (if present), and latest *_skene_triggers.sql to upstream. Proceed?" Wait for confirmation.

  4. Run push After user confirms, run uvx skene push with appropriate flags from --help output. Report which migration file was packaged (latest eligible under supabase/migrations/) and that upstream received the deploy.

Read the full file on GitHub · 50 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. 7d ago First seen · 50 lines · 47 tokens per session scan A bcf8f520beed

Subscribe to this mod's changes

deploy-telemetry is a skill published in the GitHub repository SkeneTechnologies/skene (122 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 669 once invoked, about $0.0002 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-08-30.

Analytics and metricsai-toolsanthropicautomationclicli-toolcode-documentation
Related

Other skills, from other repositories

humanizer

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague…

profclaw/profclaw · 92 tokens

session-logs

Search, browse, and analyze session history to recall past conversations, decisions, and completed work.

profclaw/profclaw · 22 tokens

api-tester

Test HTTP APIs, validate responses, generate test suites, and diagnose API issues.

profclaw/profclaw · 19 tokens

coding-agent

Delegate coding tasks to background agent sessions - build features, refactor code, review PRs, and run parallel workstreams.

profclaw/profclaw · 27 tokens

docker-ops

Container management, image building, Docker Compose orchestration, and deployment operations.

profclaw/profclaw · 18 tokens

healthcheck

System health monitoring and diagnostics - checks profClaw API, Redis, Docker, disk, memory, and processes with actionable status reports.

profclaw/profclaw · 29 tokens