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 SkeneTechnologies/skene --skill deploy-telemetrygit clone --depth 1 https://github.com/SkeneTechnologies/skeneWrote 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/skenetechnologies/skene/deploy-telemetry)<a href="https://agentmods.dev/skills/skenetechnologies/skene/deploy-telemetry"><img src="https://agentmods.dev/badge/skills/skenetechnologies/skene/deploy-telemetry/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/skenetechnologies/skene/deploy-telemetry"><img src="https://agentmods.dev/badge/skills/skenetechnologies/skene/deploy-telemetry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 15 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
- medium MCP Rug Pull · line 20 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
- medium MCP Rug Pull · line 23 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
- medium MCP Rug Pull · line 25 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
- medium MCP Rug Pull · line 29 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
- medium MCP Rug Pull · line 33 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
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.00047 | $0.00669 |
| Opus 5.5 | $0.00019 | $0.00268 |
| Sonnet 5.5 | $0.00009 | $0.00134 |
| Haiku 4.5 | $0.00005 | $0.00067 |
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 1mo 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 — 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 POSTsskene-context/engine.yaml,{output_dir}/feature-registry.jsonwhen present, and the latest trigger migration to Skene Cloud (it does not generate SQL; runuvx skene buildfirst if artifacts are missing).
Steps
-
Discover CLI options Run
uvx skene push --helpto see available flags. Use only flags that appear in the output. -
Verify prerequisites
skene-context/engine.yamlmust exist; trigger SQL lives undersupabase/migrations/as*_skene_triggers.sqlafteruvx 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; legacyskene/feature-registry.jsonauto-detected). If missing, push still runs but omits the registry untilbuildcreates it. - If engine or migrations are missing: tell the user to run
uvx skene buildfirst, then retry deploy. ls supabase/ 2>/dev/null— if missing: "No Supabase directory. Set up Supabase first."
-
Ask user to confirm Tell the user: "
uvx skene pushuploads engine, feature-registry.json (if present), and latest*_skene_triggers.sqlto upstream. Proceed?" Wait for confirmation. -
Run push After user confirms, run
uvx skene pushwith appropriate flags from --help output. Report which migration file was packaged (latest eligible undersupabase/migrations/) and that upstream received the deploy.
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.
- 1mo ago First seen · 50 lines · 47 tokens per session scan A bcf8f520beed
deploy-telemetry is a skill published in the GitHub repository SkeneTechnologies/skene (126 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 669 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
ai-session-search
Search, recover, inspect, export, and analyze local AI session history with AI Session Search (aise) across Claude Code, Claude Desktop local agent, Codex, Cursor, Antigravity, Pi coding agent, Prime Agent, Google AI Studio, and Gemini CLI. Use when asked to "find prior AI work", "recover context after compaction"…
cli2skill
Turn any CLI or MCP server into an Agent Skill. Use when you want to replace an MCP server with a zero-overhead CLI skill, or generate a skill from any command-line tool's --help output.
burnd-analyze-spend
Analyze your OpenClaw API spend — total cost, cost last 7 days, top cost leaks by model and provider, and concrete steps to reduce your bill. Use when the user asks about their AI spending, costs, budget, or which models are costing the most.
brain-log
Show brain sync and evolution history.
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…
healthcheck
System health monitoring and diagnostics - checks profClaw API, Redis, Docker, disk, memory, and processes with actionable status reports.